Triple
T28984632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBU World Cup |
E734643
|
entity |
| Predicate | hasIndividualClassification |
P196582
|
FINISHED |
| Object | overall individual standings |
—
|
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: overall individual standings | Statement: [IBU World Cup, hasIndividualClassification, overall individual standings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndividualClassification Context triple: [IBU World Cup, hasIndividualClassification, overall individual standings]
-
A.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
isIndividualOf
Indicates that a specific entity is an individual instance or member of a broader class, category, or group.
-
C.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
D.
usesClassificationCriteria
Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate another entity.
-
E.
hasTeamClassification
Indicates that an entity is assigned a specific team-based category or classification.
- 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_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
| PDg | Predicate description generation | batch_69fe5d580d7c819097cb18d438b01d08 |
completed | May 8, 2026, 10:02 p.m. |
Created at: April 28, 2026, 9:13 a.m.