Triple
T8364501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champions on Ice |
E197091
|
entity |
| Predicate | featuredParticipants |
P6467
|
FINISHED |
| Object | Olympic figure skating 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: Olympic figure skating champions | Statement: [Champions on Ice, featuredParticipants, Olympic figure skating champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredParticipants Context triple: [Champions on Ice, featuredParticipants, Olympic figure skating champions]
-
A.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
B.
notableParticipant
chosen
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
C.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
D.
participant
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
-
E.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808a67f88190849152102bfeb574 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.