Triple
T8919989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witney United F.C. |
E212388
|
entity |
| Predicate | playedInLeagueSystem |
P2209
|
FINISHED |
| Object | English football league system |
—
|
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: English football league system | Statement: [Witney United F.C., playedInLeagueSystem, English football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedInLeagueSystem Context triple: [Witney United F.C., playedInLeagueSystem, English football league system]
-
A.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
B.
leaguePlayedIn
chosen
Indicates that a sports team or player has participated in competitions within a particular league.
-
C.
playedInConference
Indicates that an entity (typically a team or player) participated in games within a specific conference during a season or time period.
-
D.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
E.
isPartOfLeague
Indicates that an entity belongs to, participates in, or is a member of a particular league.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc664f099c8190be6d20a4574212ca |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.