Triple
T8188845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brilliant Hall |
E191253
|
entity |
| Predicate | locatedWithinComplex |
P57262
|
FINISHED |
| Object | historic core of Tehran |
—
|
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: historic core of Tehran | Statement: [Brilliant Hall, locatedWithinComplex, historic core of Tehran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinComplex Context triple: [Brilliant Hall, locatedWithinComplex, historic core of Tehran]
-
A.
positionWithinComplex
Indicates that one entity is located inside or forms a component part of a larger complex or compound structure.
-
B.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
C.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
D.
existsWithin
chosen
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da0e1288190b9c7c1d3b9a98830 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.