Triple
T27686945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congreso–Plaza de Mayo axis |
E698056
|
entity |
| Predicate | notableBuildingAlong |
P57645
|
FINISHED |
| Object | Palacio Barolo |
—
|
NE NERFINISHED |
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: Palacio Barolo | Statement: [Congreso–Plaza de Mayo axis, notableBuildingAlong, Palacio Barolo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuildingAlong Context triple: [Congreso–Plaza de Mayo axis, notableBuildingAlong, Palacio Barolo]
-
A.
notableBuildingAssociated
chosen
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
notableConstructionCenter
Indicates that a place serves as a significant hub or focal point for construction activity or construction-related operations.
-
D.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 27, 2026, 2:50 p.m.