Triple
T24798579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nogales border crossing |
E620456
|
entity |
| Predicate | hasInspectionType |
P16808
|
FINISHED |
| Object | immigration inspection |
—
|
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: immigration inspection | Statement: [Nogales border crossing, hasInspectionType, immigration inspection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInspectionType Context triple: [Nogales border crossing, hasInspectionType, immigration inspection]
-
A.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
-
B.
hasInspectionBody
Indicates that an entity is associated with or overseen by a specific organization responsible for inspecting or auditing it.
-
C.
hasAnalysisType
Indicates that one entity is associated with, or characterized by, a specific type or category of analysis applied to it.
-
D.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasTaskType
Indicates that an entity is associated with or classified under a specific type or category of task.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:49 a.m.