Triple
T34806647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Nacimiento, Coahuila, Mexico |
E1003376
|
entity |
| Predicate | borderRelatedTo |
P224
|
FINISHED |
| Object | Texas |
—
|
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: Texas | Statement: [El Nacimiento, Coahuila, Mexico, borderRelatedTo, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRelatedTo Context triple: [El Nacimiento, Coahuila, Mexico, borderRelatedTo, Texas]
-
A.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
B.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
borderConceptUsedBy
Indicates that a conceptual boundary or limit is employed or referenced by another entity in its definition, use, or interpretation.
-
D.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: May 3, 2026, 3:59 p.m.