Triple
T33614473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subteniente López |
E861078
|
entity |
| Predicate | crossBorderPointFor |
P166637
|
FINISHED |
| Object | Mexico |
—
|
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: Mexico | Statement: [Subteniente López, crossBorderPointFor, Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderPointFor Context triple: [Subteniente López, crossBorderPointFor, Mexico]
-
A.
crossBorderNode
Indicates a connection or element that spans or links entities across a defined boundary or border.
-
B.
crossBorderGatewayFor
chosen
Indicates that one entity functions as a gateway enabling traffic or interaction to cross a border or boundary for another entity.
-
C.
crossBorderSection
Indicates a section or segment that extends across or passes from one jurisdiction, region, or country into another.
-
D.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
E.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:41 a.m.