Triple
T15168598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 European Cup Final |
E362424
|
entity |
| Predicate | winnerConsecutiveTitles |
P66338
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1976 European Cup Final, winnerConsecutiveTitles, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerConsecutiveTitles Context triple: [1976 European Cup Final, winnerConsecutiveTitles, 3]
-
A.
consecutiveLeagueTitles
Indicates that one entity has won league titles in successive seasons without interruption.
-
B.
consecutiveTitlesForChampion
chosen
Indicates that a champion has won multiple titles in succession without interruption.
-
C.
winnerTitleCount
Indicates the number of titles or championships an entity has won.
-
D.
consecutiveLeagueTitlesPeriod
Indicates a time span during which a team or entity wins league titles in consecutive seasons without interruption.
-
E.
winnerTitleRecord
Indicates that a record documents the title or achievement associated with an entity that has won a particular contest, award, or 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064dba588190a4341775b472a6d3 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.