Triple
T17099377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Division 1961–62 |
E414938
|
entity |
| Predicate | titleDecidedBy |
P89197
|
FINISHED |
| Object | points total over the season |
—
|
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: points total over the season | Statement: [First Division 1961–62, titleDecidedBy, points total over the season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleDecidedBy Context triple: [First Division 1961–62, titleDecidedBy, points total over the season]
-
A.
titleDecidedOn
Indicates that a final decision has been made regarding the title assigned to an entity or work.
-
B.
titleDeciderFor
Indicates that one entity is responsible for determining or assigning the title associated with another entity.
-
C.
decidesTitle
Indicates that one entity determines or selects the official title or name assigned to another entity.
-
D.
titleDecidingMatch
Indicates a match whose outcome determines the winner of a title or championship.
-
E.
decidingFactorForTitle
chosen
Indicates that something serves as the key criterion or primary reason for determining or awarding a particular title.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc00880481909cc0dbc169663a41 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.