Triple
T32998723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Cup 1972–73 |
E844301
|
entity |
| Predicate | hasReplayMatches |
P154157
|
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 1972–73, hasReplayMatches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplayMatches Context triple: [Football League Cup 1972–73, hasReplayMatches, yes]
-
A.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
B.
includedReplayMatches
Indicates that certain replay matches are contained within or selected as part of a specified set, collection, or context.
-
C.
hasReplayRuleHistorically
Indicates that a replay rule applied to an entity at some point in the past, regardless of whether it is still in effect now.
-
D.
hasReplayStage
chosen
Indicates that an event, process, or competition includes a replay phase or stage in its structure.
-
E.
isReplay
Indicates that an event, action, or content instance is a repeated playback or reproduction of a previously occurring original.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a033029023481909d9fa4a76b954879 |
completed | May 12, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_6a032d9f1fa48190bd1c94a8f930d02c |
completed | May 12, 2026, 1:39 p.m. |
Created at: May 1, 2026, 1:22 a.m.