Triple
T15797433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciudad Cuauhtémoc, Chiapas |
E383016
|
entity |
| Predicate | hasBorderServices |
P72412
|
FINISHED |
| Object | money exchange offices |
—
|
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: money exchange offices | Statement: [Ciudad Cuauhtémoc, Chiapas, hasBorderServices, money exchange offices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderServices Context triple: [Ciudad Cuauhtémoc, Chiapas, hasBorderServices, money exchange offices]
-
A.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
-
B.
hasBorderFacilities
chosen
Indicates that one entity possesses or is equipped with facilities or infrastructure used for managing or servicing a border with another entity.
-
C.
hasBorderFacilityType
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
-
D.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
E.
hasOwnBorderControls
Indicates that an entity independently manages and enforces its own border control policies and procedures, separate from those of other entities.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4def80481908f72733ce9133bc6 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.