Triple
T31651044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 Winter Olympics Nordic combined events |
E807730
|
entity |
| Predicate | teamEventSize |
P172064
|
FINISHED |
| Object | 4 athletes per team |
—
|
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 athletes per team | Statement: [2002 Winter Olympics Nordic combined events, teamEventSize, 4 athletes per team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamEventSize Context triple: [2002 Winter Olympics Nordic combined events, teamEventSize, 4 athletes per team]
-
A.
teamSizeVariantOf
Indicates that one entity represents a variation of another entity specifically in terms of team size configuration or composition.
-
B.
teamDuringEvent
Indicates that a particular team is associated with, participates in, or is active during a specified event.
-
C.
teamSizeFormat
Indicates how the size of a team is represented or formatted (e.g., as a number, range, or categorized label).
-
D.
clubSize
Indicates the number of members or participants in a given club.
-
E.
teamCountType
Indicates how the number of teams is categorized or measured within a given context.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a959b4948190999f86efb6244d0e |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:53 p.m.