Triple
T5604297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Biathlon Union |
E147193
|
entity |
| Predicate | governsEventType |
P760
|
FINISHED |
| Object | individual biathlon races |
—
|
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: individual biathlon races | Statement: [International Biathlon Union, governsEventType, individual biathlon races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsEventType Context triple: [International Biathlon Union, governsEventType, individual biathlon races]
-
A.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
servesEventType
Indicates that an entity provides or supports a particular type or category of event.
-
C.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
D.
governsActionBy
Indicates that one entity exercises control, authority, or regulatory power over the actions or behavior of another entity.
-
E.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020f9408481908cf006074c726301 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.