Triple
T4232088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de la Constitución |
E94602
|
entity |
| Predicate | locatedInTheCenterOf |
P25976
|
FINISHED |
| Object | historic center of Guatemala City |
—
|
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 center of Guatemala City | Statement: [Plaza de la Constitución, locatedInTheCenterOf, historic center of Guatemala City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheCenterOf Context triple: [Plaza de la Constitución, locatedInTheCenterOf, historic center of Guatemala City]
-
A.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
hasCityCentreLocation
chosen
Indicates that something is located in, or directly associated with, the central area of a city.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
centralCeremonyLocation
Indicates the place that serves as the primary or focal site where a ceremony is held.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e642aac8190977dd101e27afcbb |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.