Triple
T36254827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Athletes from Russia |
E891903
|
entity |
| Predicate | medalEligibility |
P184818
|
FINISHED |
| Object | eligible for medals |
—
|
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: eligible for medals | Statement: [Olympic Athletes from Russia, medalEligibility, eligible for medals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medalEligibility Context triple: [Olympic Athletes from Russia, medalEligibility, eligible for medals]
-
A.
qualifiedForOlympicGames
Indicates that an entity has met the necessary standards or criteria to participate in the Olympic Games.
-
B.
OlympicStatus
Indicates that an entity holds a particular status or role in relation to the Olympic Games (e.g., being an Olympic sport, event, athlete, or host).
-
C.
medalistAtEvent
Indicates that an entity has won a medal in a specified event.
-
D.
olympicEligibilityRule
Indicates that a specific rule or condition determines whether an athlete or team is eligible to participate in the Olympic Games.
-
E.
eligibleNOCs
Indicates that certain entities (e.g., organizations, individuals, or codes) qualify as valid or permitted under a specified set of NOC-related rules or criteria.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5fd3f8481908b9380f82a2310f0 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.