Triple
T31651048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 Winter Olympics Nordic combined events |
E807730
|
entity |
| Predicate | crossCountryDistanceTeam |
P27047
|
FINISHED |
| Object | 4 × 5 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 × 5 km relay | Statement: [2002 Winter Olympics Nordic combined events, crossCountryDistanceTeam, 4 × 5 km relay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossCountryDistanceTeam Context triple: [2002 Winter Olympics Nordic combined events, crossCountryDistanceTeam, 4 × 5 km relay]
-
A.
crossCountryLevel
Indicates the level or degree of involvement, skill, or difficulty associated with cross-country activities or events.
-
B.
crossCountryNationalChampionships
Indicates that an entity has won or holds national championship titles in cross-country competition.
-
C.
raceDistanceType
chosen
Indicates the specific type or category of distance over which a race is conducted.
-
D.
distancePerRace
Indicates the total distance covered in a single race event or instance.
-
E.
trackRecordDistance
Indicates that one entity holds the record for the greatest distance achieved in a particular tracking or performance context.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 30, 2026, 10:53 p.m.