Triple
T30682530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Championship 2013–14 |
E781091
|
entity |
| Predicate | playOffFinalScore |
P119380
|
FINISHED |
| Object | 1–0 |
—
|
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: 1–0 | Statement: [Football League Championship 2013–14, playOffFinalScore, 1–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playOffFinalScore Context triple: [Football League Championship 2013–14, playOffFinalScore, 1–0]
-
A.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
B.
playoffResult
Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
-
C.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
D.
postseasonMeetingScore
chosen
Indicates the score or outcome of a competitive meeting (such as a game or match) that takes place during a postseason phase.
-
E.
finalFullTimeScore
Indicates the final total score achieved by each side at the end of a full-time game or match.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:33 p.m.