Triple
T26229993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Leones |
E656007
|
entity |
| Predicate | associatedSupporters |
P74897
|
FINISHED |
| Object | Athletic Club 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: Athletic Club fans | Statement: [Los Leones, associatedSupporters, Athletic Club fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSupporters Context triple: [Los Leones, associatedSupporters, Athletic Club fans]
-
A.
associatedWithSupporters
chosen
Indicates that an entity has a relationship or connection with individuals or groups who support or advocate for it.
-
B.
hasSupportersIn
Indicates that an entity is backed or endorsed by people or groups located within a specified place or region.
-
C.
supporters
Indicates a relationship where one entity backs, endorses, or actively helps another entity, cause, or position.
-
D.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
E.
usedBySupporters
Indicates that something is utilized or employed by supporters of a person, group, cause, or entity.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: April 26, 2026, 8:59 p.m.