Triple
T37360704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 1994–95 |
E927567
|
entity |
| Predicate | winnerUnbeaten |
P102067
|
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: [UEFA Champions League 1994–95, winnerUnbeaten, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerUnbeaten Context triple: [UEFA Champions League 1994–95, winnerUnbeaten, true]
-
A.
undefeatedTeamInFinal
chosen
Indicates that a team reached the final match of a competition and did so without having lost any game up to and including that final.
-
B.
neverWonBy
Indicates that a particular entity has at no time in the past been the winner or recipient of something as a result of another specified entity.
-
C.
winnerDam
Indicates that the subject entity is the dam (mother) of an offspring that has won a specified race or competition.
-
D.
winnerWith
Indicates that one entity is the winner in a context or event specifically in association or combination with another entity.
-
E.
ownedWinnerOf
Indicates that an entity owns or possesses the winner of a specified competition, contest, or event.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:16 p.m.