Triple
T23688839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Cup 2000–01 |
E585242
|
entity |
| Predicate | winnerAlsoWon |
P144984
|
FINISHED |
| Object | FA Cup 2000–01 |
—
|
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: FA Cup 2000–01 | Statement: [Football League Cup 2000–01, winnerAlsoWon, FA Cup 2000–01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerAlsoWon Context triple: [Football League Cup 2000–01, winnerAlsoWon, FA Cup 2000–01]
-
A.
winnerPreviouslyWon
Indicates that the winner has won the same or a related contest/event at least once before.
-
B.
winnerAssociated
Indicates that there is a relevant connection or affiliation between a winner and another entity in the context of a particular event or competition.
-
C.
winnerCreditedAs
Indicates the name or designation under which the winner is officially recorded or credited for a particular award, contest, or achievement.
-
D.
bearerAlsoWon
chosen
Indicates that the bearer of something (e.g., a title, award, or object) also won another specified competition, prize, or distinction.
-
E.
ownedWinnerOf
Indicates that an entity owns or possesses the winner of a specified competition, contest, or event.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c0a218819096c2d174b004c47d |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.