Triple
T8167050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenida de Mayo |
E190717
|
entity |
| Predicate | hasMaximumStructureHeightRegulation |
P81055
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Avenida de Mayo, hasMaximumStructureHeightRegulation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumStructureHeightRegulation Context triple: [Avenida de Mayo, hasMaximumStructureHeightRegulation, yes]
-
A.
hasHighestStructure
Indicates that an entity possesses the tallest or most elevated structural feature compared to all other relevant entities in a given context.
-
B.
structureHeight
Indicates that a structure has a specific vertical measurement or height.
-
C.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
D.
hasMaximumThickness
Indicates that an entity possesses a specified upper limit on its thickness.
-
E.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
- F. None of above. chosen
Provenance (4 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb46680fac81908df134df9bf84915 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb40a017608190b6b48cf60335fa8d |
completed | March 31, 2026, 3:33 a.m. |
Created at: March 30, 2026, 5:39 p.m.