Triple
T27975643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | میدان آزادی |
E706480
|
entity |
| Predicate | دارای عنصر معماری شاخص |
P6684
|
FINISHED |
| Object | برج آزادی با معماری تلفیقی ایرانی-مدرن |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: برج آزادی با معماری تلفیقی ایرانی-مدرن | Statement: [میدان آزادی, دارای عنصر معماری شاخص, برج آزادی با معماری تلفیقی ایرانی-مدرن]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: دارای عنصر معماری شاخص Context triple: [میدان آزادی, دارای عنصر معماری شاخص, برج آزادی با معماری تلفیقی ایرانی-مدرن]
-
A.
دارای سازه شاخص
Indicates that an entity possesses or includes a prominent or distinctive structural feature.
-
B.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
D.
آثار شاخص
Indicates that an entity has notable or distinguished works or creations associated with it.
-
E.
architectureProfileOf
Indicates that one entity serves as the architectural specification, style, or structural design profile that characterizes or defines another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 7:41 p.m.