Triple
T31323923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darya |
E798827
|
entity |
| Predicate | notableInSportThroughBearer |
P10392
|
FINISHED |
| Object | biathlon |
—
|
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: biathlon | Statement: [Darya, notableInSportThroughBearer, biathlon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInSportThroughBearer Context triple: [Darya, notableInSportThroughBearer, biathlon]
-
A.
notableAthlete
chosen
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
B.
notableCharacterSport
Indicates that a notable character is associated with, participates in, or is prominently linked to a particular sport.
-
C.
notableBearerLeague
Indicates that a league is notably associated with or prominently represented by a particular bearer (such as a team, player, or entity).
-
D.
notableMedalSport
Indicates that the sport specified is the one in which the entity received a notable medal or award.
-
E.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.