Triple
T26390057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Liefering |
E663385
|
entity |
| Predicate | feederClubFor |
P56869
|
FINISHED |
| Object | FC Red Bull Salzburg |
—
|
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 Red Bull Salzburg | Statement: [FC Liefering, feederClubFor, FC Red Bull Salzburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feederClubFor Context triple: [FC Liefering, feederClubFor, FC Red Bull Salzburg]
-
A.
servesClub
Indicates that an entity provides service, work, or support to a particular club or organization.
-
B.
feedsClubsInto
Indicates that one entity supplies or directs clubs into another entity as input or participants.
-
C.
mainFeederOf
chosen
Indicates that one entity serves as the primary source or supplier of resources, energy, or input to another entity.
-
D.
feederSystem
Indicates a system or mechanism that supplies or feeds resources, materials, or inputs into another process, component, or structure.
-
E.
feederDistrict
Indicates that one district serves as a primary source of students or participants that move on to another district (e.g., for schooling or services).
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610be3e848190b7acb7675e37e1f5 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:25 p.m.