Triple
T34871691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europass Gloria |
E1005767
|
entity |
| Predicate | specialEditionFor |
P18253
|
FINISHED |
| Object | UEFA Euro 2008 final match |
—
|
NE NERFINISHED |
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: UEFA Euro 2008 final match | Statement: [Europass Gloria, specialEditionFor, UEFA Euro 2008 final match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialEditionFor Context triple: [Europass Gloria, specialEditionFor, UEFA Euro 2008 final match]
-
A.
specialEdition
chosen
Indicates that an item is a distinct, limited, or enhanced version of a standard release, often with unique features, packaging, or content.
-
B.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
C.
expoEdition
Indicates the specific edition or iteration of an exposition or expo event to which something is related.
-
D.
overseesSpecialEditionsOf
Indicates that one entity has responsibility for supervising, managing, or directing the production or publication of special editions of another entity.
-
E.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4 p.m.