Triple
T23660699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tijuana Cartel |
E584435
|
entity |
| Predicate | smugglingRouteFocus |
P75275
|
FINISHED |
| Object | California–Baja California border |
—
|
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: California–Baja California border | Statement: [Tijuana Cartel, smugglingRouteFocus, California–Baja California border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smugglingRouteFocus Context triple: [Tijuana Cartel, smugglingRouteFocus, California–Baja California border]
-
A.
hasSmugglingRoutes
chosen
Indicates that an entity maintains or controls secret or illegal transportation paths used to move goods or people covertly.
-
B.
smugglingMethod
Indicates the method or technique used to illegally transport goods or people across borders or through restricted areas.
-
C.
borderStreet
Indicates that a street forms or lies along the boundary between two geographic areas or properties.
-
D.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
E.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35f03448190834991c2a65ef0e4 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.