Triple
T2830116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuevo Laredo |
E62214
|
entity |
| Predicate | hasPortOfEntryType |
P13728
|
FINISHED |
| Object | land port of entry |
—
|
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: land port of entry | Statement: [Nuevo Laredo, hasPortOfEntryType, land port of entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortOfEntryType Context triple: [Nuevo Laredo, hasPortOfEntryType, land port of entry]
-
A.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
B.
hasBorderControlStatus
chosen
Indicates the type or condition of border control that applies to a given entity or location.
-
C.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
D.
hasBorderCrossingFunction
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
E.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebbde4881908dfa78e28c7018e0 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.