Triple
T37360710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 1994–95 |
E927567
|
entity |
| Predicate | titleHoldersEntry |
P201385
|
FINISHED |
| Object | AC Milan entered as defending champions |
—
|
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: AC Milan entered as defending champions | Statement: [UEFA Champions League 1994–95, titleHoldersEntry, AC Milan entered as defending champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHoldersEntry Context triple: [UEFA Champions League 1994–95, titleHoldersEntry, AC Milan entered as defending champions]
-
A.
titleHolders
Indicates that one or more entities currently or formerly hold a specified title, position, or honor.
-
B.
titleHoldersWere
Indicates that certain entities previously held a specified title or position during a past period.
-
C.
titleHoldersLinkedTo
Indicates that two or more entities are connected through holding, sharing, or transferring the same title or position.
-
D.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
E.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
| PDg | Predicate description generation | batch_69ffef8003c081909ec2413b4ea08d43 |
completed | May 10, 2026, 2:37 a.m. |
Created at: May 3, 2026, 4:16 p.m.