Triple
T23843499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Cup 1983–84 |
E591052
|
entity |
| Predicate | finalRequiredReplay |
P147704
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Football League Cup 1983–84, finalRequiredReplay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalRequiredReplay Context triple: [Football League Cup 1983–84, finalRequiredReplay, yes]
-
A.
finalReplayRequired
chosen
Indicates that a concluding or definitive replay of an event or process is required to be performed.
-
B.
finalReplayScore
Indicates the score or result achieved at the end of a replayed event, game, or scenario.
-
C.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
D.
finalReplayVenue
Indicates the venue where a final match is replayed after an initial final did not produce a decisive result.
-
E.
finalReplayLoser
Indicates that an entity is the participant who lost in the final replay (i.e., a rematch or replayed final) of a competition or contest.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c8898a0c8190b4d55852fc30260f |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:09 p.m.