Triple
T32240265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980–81 Football League First Division |
E823593
|
entity |
| Predicate | titleRaceDescription |
P197671
|
FINISHED |
| Object | closely contested |
—
|
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: closely contested | Statement: [1980–81 Football League First Division, titleRaceDescription, closely contested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRaceDescription Context triple: [1980–81 Football League First Division, titleRaceDescription, closely contested]
-
A.
titleRaceRival
Indicates a competitive rivalry between entities specifically centered on winning or defending a title or championship.
-
B.
titleDescription
Indicates that one entity serves as a descriptive or explanatory subtitle or summary associated with the title of another entity.
-
C.
titleHolderRace
Indicates the race or racial identity of the entity that holds a particular title.
-
D.
raceName
Indicates the specific race or competition designation associated with an entity or event.
-
E.
featuresRaceBetween
Indicates that an event or context includes or showcases a competitive race occurring between participants.
- F. None of above. chosen
Provenance (4 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 1, 2026, 12:40 a.m.