Triple
T38565066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of Veracruz |
E928190
|
entity |
| Predicate | hasMainSquareNearby |
P7888
|
FINISHED |
| Object | Plaza de Armas of Veracruz |
E911885
|
NE 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: Plaza de Armas of Veracruz | Statement: [Cathedral of Veracruz, hasMainSquareNearby, Plaza de Armas of Veracruz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSquareNearby Context triple: [Cathedral of Veracruz, hasMainSquareNearby, Plaza de Armas of Veracruz]
-
A.
hasMainBuildingNear
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
-
B.
hasPublicSquareInFront
Indicates that a building or structure has a public square located directly in front of it.
-
C.
mainSquare
Indicates that a location serves as the primary or central public square of a town or city.
-
D.
hasFamousSquare
Indicates that a place possesses or contains a well-known public square associated with it.
-
E.
hasNearbySquare
chosen
Indicates that one entity has at least one square-shaped entity located close to it in space.
- F. None of above.
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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41f434bb3081909694ba026a81b463 |
completed | June 29, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.