Triple
T1117276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Leones |
E11128
|
entity |
| Predicate | usedAsHomeNicknameBy |
P23575
|
FINISHED |
| Object | Industriales fans |
—
|
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: Industriales fans | Statement: [Los Leones, usedAsHomeNicknameBy, Industriales fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsHomeNicknameBy Context triple: [Los Leones, usedAsHomeNicknameBy, Industriales fans]
-
A.
localNickname
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
B.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
C.
nameUsedToAccommodate
Indicates that a particular name was previously used to refer to or accommodate an entity, but is no longer its current or primary name.
-
D.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
E.
fandomNickname
chosen
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.