Triple
T31783476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English First Division 1968–69 |
E811266
|
entity |
| Predicate | championsFirstTitle |
P130769
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [English First Division 1968–69, championsFirstTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championsFirstTitle Context triple: [English First Division 1968–69, championsFirstTitle, true]
-
A.
seasonChampionsFirstTitle
chosen
Indicates that the champions of a given season won their first-ever title in that season.
-
B.
firstChampions
Indicates that the subject entities are the initial or earliest champions (winners or title holders) in a given competition, event, or context.
-
C.
winningTeamFirstTitle
Indicates that the winning team is achieving its first-ever title in the relevant competition or context.
-
D.
championsTitleWonBy
Indicates that a particular championship title is held or has been won by a specific entity.
-
E.
championConsecutiveTitlesStart
Indicates the point in time or event at which an entity begins a streak of winning championship titles in consecutive editions of a competition.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 11:37 p.m.