Triple
T26390222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull multi-club system |
E663390
|
entity |
| Predicate | hasFormerClub |
P172096
|
FINISHED |
| Object | Red Bull Ghana |
—
|
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: Red Bull Ghana | Statement: [Red Bull multi-club system, hasFormerClub, Red Bull Ghana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerClub Context triple: [Red Bull multi-club system, hasFormerClub, Red Bull Ghana]
-
A.
hasFormerTeam
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
B.
associatedWithFormerClubName
Indicates a relationship where an entity is linked to the previous or former name of a club.
-
C.
laterRepresentedClub
Indicates that an individual went on to represent a particular club at a later time than the contextually referenced period or affiliation.
-
D.
clubFormerName
Indicates that a sports club previously operated under a different official name.
-
E.
predecessorClubAssociation
Indicates that one club or team previously existed in place of, or was succeeded by, another club or team in an organizational or historical lineage.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 26, 2026, 11:25 p.m.