Triple
T23660684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tijuana Cartel |
E584435
|
entity |
| Predicate | familyControl |
P4852
|
FINISHED |
| Object | Arellano Félix family |
—
|
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: Arellano Félix family | Statement: [Tijuana Cartel, familyControl, Arellano Félix family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyControl Context triple: [Tijuana Cartel, familyControl, Arellano Félix family]
-
A.
familyControlled
chosen
Indicates that an entity is owned or effectively governed by one or more members of the same family, who hold decisive control over its decisions or operations.
-
B.
parentStudio
Indicates that one studio serves as the parent or owning studio of another studio.
-
C.
familyRule
Indicates a rule, norm, or guideline that governs relationships or behavior within a family context.
-
D.
familyAuthority
Indicates that one entity holds recognized decision-making power or control over another within a family or household context.
-
E.
familyPolicyOrientation
Indicates how a policy or actor is oriented toward family-related issues, such as the extent to which it supports, prioritizes, or affects families and family life.
- 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.