Triple
T21960593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1971–72 European Cup |
E542316
|
entity |
| Predicate | consecutiveTitlesForAjax |
P87395
|
FINISHED |
| Object | third consecutive title |
—
|
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: third consecutive title | Statement: [1971–72 European Cup, consecutiveTitlesForAjax, third consecutive title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecutiveTitlesForAjax Context triple: [1971–72 European Cup, consecutiveTitlesForAjax, third consecutive title]
-
A.
consecutiveTitlesForChampion
Indicates that a champion has won multiple titles in succession without interruption.
-
B.
consecutiveTitleNumber
Indicates that one entity’s title number immediately follows another’s in a sequential ordering.
-
C.
consecutiveTitleNumberForChampion
chosen
Indicates that the associated number represents how many titles a champion has won consecutively up to that point.
-
D.
consecutiveLeagueTitles
Indicates that one entity has won league titles in successive seasons without interruption.
-
E.
consecutiveLeagueTitlesPeriod
Indicates a time span during which a team or entity wins league titles in consecutive seasons without interruption.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12455e99c819092ec59fe571f814e |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8 p.m.