Triple
T13257311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wide World of Sports |
E315691
|
entity |
| Predicate | coveredEventType |
P38977
|
FINISHED |
| Object | Olympic sports |
—
|
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 sports | Statement: [Wide World of Sports, coveredEventType, Olympic sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredEventType Context triple: [Wide World of Sports, coveredEventType, Olympic sports]
-
A.
associatedEventType
chosen
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
B.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
C.
significantEventType
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
D.
investigatedEvent
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
E.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:25 p.m.