Triple
T33614491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subteniente López |
E861078
|
entity |
| Predicate | hasBorderControlAuthority |
P194091
|
FINISHED |
| Object | Mexican customs service |
—
|
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: Mexican customs service | Statement: [Subteniente López, hasBorderControlAuthority, Mexican customs service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderControlAuthority Context triple: [Subteniente López, hasBorderControlAuthority, Mexican customs service]
-
A.
hasBorderControlBy
Indicates that the border of one entity is monitored, regulated, or managed by another entity.
-
B.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
C.
hasBorderControlFacility
Indicates that one location possesses an official facility responsible for managing and controlling border crossings to or from another location.
-
D.
hasBorderControlHistory
Indicates that there is a documented history of actions, policies, or events related to border control involving the associated entities.
-
E.
hasBorderControlIssues
Indicates that there are problems, weaknesses, or irregularities in the enforcement or management of border controls between entities.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: May 1, 2026, 1:41 a.m.