Triple
T24020663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salón Amarillo |
E594808
|
entity |
| Predicate | locatedInBuildingFacing |
P143279
|
FINISHED |
| Object | Plaza de la Independencia, Quito |
—
|
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: Plaza de la Independencia, Quito | Statement: [Salón Amarillo, locatedInBuildingFacing, Plaza de la Independencia, Quito]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBuildingFacing Context triple: [Salón Amarillo, locatedInBuildingFacing, Plaza de la Independencia, Quito]
-
A.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
B.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
-
C.
locatedInSectionOfBuilding
Indicates that one entity is situated within a specific section or area of a building.
-
D.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
E.
locationInArchitecture
chosen
Indicates the spatial position or placement of one architectural element or feature within or relative to another architectural structure or context.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5aaf8588190b266557d573504b8 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:43 p.m.