Triple
T2067029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBX |
E45924
|
entity |
| Predicate | borderControlSide |
P35156
|
FINISHED |
| Object | U.S. customs and immigration |
—
|
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: U.S. customs and immigration | Statement: [CBX, borderControlSide, U.S. customs and immigration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderControlSide Context triple: [CBX, borderControlSide, U.S. customs and immigration]
-
A.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
B.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
C.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
D.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
E.
hasBorderGuardingMandateWith
Indicates that one entity has an official responsibility or mandate to guard, monitor, or secure a border in cooperation or association with another entity.
- F. None of above. chosen
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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f236f08190b602d337afb1880f |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:40 p.m.