Triple
T37360673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 1994–95 |
E927567
|
entity |
| Predicate | hasFinalDate |
P82025
|
FINISHED |
| Object | 1995-05-24 |
—
|
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: 1995-05-24 | Statement: [UEFA Champions League 1994–95, hasFinalDate, 1995-05-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalDate Context triple: [UEFA Champions League 1994–95, hasFinalDate, 1995-05-24]
-
A.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
dateFinalized
chosen
Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
-
C.
hasCollectionEndDate
Indicates the date on which a collection activity, period, or process is scheduled or recorded to end.
-
D.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
E.
finalTerminationDate
Indicates the date on which an agreement, contract, or relationship is conclusively and irrevocably ended.
- 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_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
Created at: May 3, 2026, 4:16 p.m.