Triple
T11822081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Golden Player Jubilee Awards |
E281163
|
entity |
| Predicate | isRelatedEventOf |
P59649
|
FINISHED |
| Object | UEFA 50th anniversary campaign |
—
|
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: UEFA 50th anniversary campaign | Statement: [UEFA Golden Player Jubilee Awards, isRelatedEventOf, UEFA 50th anniversary campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedEventOf Context triple: [UEFA Golden Player Jubilee Awards, isRelatedEventOf, UEFA 50th anniversary campaign]
-
A.
isLinkedToEvent
chosen
Indicates that an entity has an association or connection with a specific event.
-
B.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
-
C.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
D.
relationshipToEvent
Indicates the specific way an entity is connected or related to a particular event.
-
E.
isRelatedUnit
Indicates that one unit has a defined relationship or association with another unit within a given system or 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.