Triple
T26390232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull multi-club system |
E663390
|
entity |
| Predicate | hasFeederClub |
P163879
|
FINISHED |
| Object | FC Liefering |
—
|
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: FC Liefering | Statement: [Red Bull multi-club system, hasFeederClub, FC Liefering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeederClub Context triple: [Red Bull multi-club system, hasFeederClub, FC Liefering]
-
A.
hasFeederUnion
Indicates that an entity is associated with or connected to a feeder union, typically one that supplies members, resources, or support to it.
-
B.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
C.
hasFeederTour
Indicates that an entity is associated with a secondary or supporting tour that feeds into a main event or itinerary.
-
D.
hasFeederLeagues
Indicates that an organization or competition is supplied with participants or teams from one or more lower-tier leagues that feed into it.
-
E.
hasFeederArea
Indicates that one entity serves as the source or contributing area that supplies resources, inputs, or influence to another entity.
- 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_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 26, 2026, 11:25 p.m.