Triple
T38008961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 UEFA Cup Final |
E948310
|
entity |
| Predicate | secondLegDate |
P200972
|
FINISHED |
| Object | 1974-05-29 |
—
|
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: 1974-05-29 | Statement: [1974 UEFA Cup Final, secondLegDate, 1974-05-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondLegDate Context triple: [1974 UEFA Cup Final, secondLegDate, 1974-05-29]
-
A.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
B.
secondCoupDate
Indicates the date on which an entity experienced or carried out its second coup.
-
C.
secondRoundDate
Indicates the date on which the second round of an event, process, or sequence is scheduled or occurs.
-
D.
secondPhaseStartDate
Indicates the date on which the second phase of a process, project, or activity begins.
-
E.
secondAttackDate
Indicates the date on which a second attack or follow-up assault occurred in relation to a prior initial attack.
- F. None of above. chosen
Provenance (4 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
| PDg | Predicate description generation | batch_69ffbe9c7c348190b6b72455d6a3e3d8 |
completed | May 9, 2026, 11:09 p.m. |
Created at: May 3, 2026, 4:20 p.m.