Triple
T9573669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biathlon at the 2002 Winter Olympics |
E230988
|
entity |
| Predicate | multiEvent |
P38530
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Biathlon at the 2002 Winter Olympics, multiEvent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiEvent Context triple: [Biathlon at the 2002 Winter Olympics, multiEvent, yes]
-
A.
multiEventsIncluded
chosen
Indicates that multiple distinct events are collectively contained within, or form part of, a larger event set or grouping.
-
B.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
C.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
D.
alternativeEvent
Indicates that one event serves as an alternative or substitute option to another event within the same context.
-
E.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99a94c788190a4bb5d2b676908ac |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.