Triple
T2027656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glorieta de Colón |
E44444
|
entity |
| Predicate | isMonumentAxisPoint |
P11053
|
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: [Glorieta de Colón, isMonumentAxisPoint, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonumentAxisPoint Context triple: [Glorieta de Colón, isMonumentAxisPoint, yes]
-
A.
hasInitialPointMonument
Indicates that a monument serves as the designated initial or starting point for a referenced spatial feature or boundary.
-
B.
isReferencePointFor
chosen
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
monumentState
Indicates that a monument is located within, or officially associated with, a particular state or state-level administrative region.
-
D.
isMajorAccessPointFor
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
-
E.
isMonumentalTree
Indicates that a tree is officially recognized as exceptionally significant, typically due to its age, size, rarity, historical, cultural, or ecological importance.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb911e5dc819097e40af0da4d01e7 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.