Triple
T6176879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Championship play-offs |
E137841
|
entity |
| Predicate | finalNickName |
P37280
|
FINISHED |
| Object | richest game in football |
—
|
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: richest game in football | Statement: [Football League Championship play-offs, finalNickName, richest game in football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalNickName Context triple: [Football League Championship play-offs, finalNickName, richest game in football]
-
A.
nameFinal
Indicates that this is the final or definitive name assigned to an entity, as opposed to a temporary, intermediate, or previous name.
-
B.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
C.
localNickname
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
D.
stageNickname
Indicates that one entity is the stage name or performance nickname used by another entity.
-
E.
isOfficialNicknameOf
chosen
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc87bc48190834042d9c41d5b86 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.