Triple
T28984586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish national cross-country skiing team |
E734642
|
entity |
| Predicate | relayEvent |
P166086
|
FINISHED |
| Object | 4×10 km relay |
—
|
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: 4×10 km relay | Statement: [Swedish national cross-country skiing team, relayEvent, 4×10 km relay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relayEvent Context triple: [Swedish national cross-country skiing team, relayEvent, 4×10 km relay]
-
A.
relayEvents
Indicates that one entity forwards or passes along events it receives to another entity or system.
-
B.
relayType
Indicates the specific kind or category of relay mechanism or configuration used in a system or connection.
-
C.
bearerEvent
Indicates that an entity serves as the bearer or holder in relation to a specific event or occurrence.
-
D.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
E.
relayChangeMethod
Indicates the method or mechanism by which a relay’s state or configuration is changed.
- F. None of above. chosen
Provenance (4 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f78c4d08190b68ee2b2fed19fff |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 9:13 a.m.