Triple
T36254799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Athletes from Russia |
E891903
|
entity |
| Predicate | statusOfNOC |
P200673
|
FINISHED |
| Object | suspended |
—
|
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: suspended | Statement: [Olympic Athletes from Russia, statusOfNOC, suspended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfNOC Context triple: [Olympic Athletes from Russia, statusOfNOC, suspended]
-
A.
hasNOC
Indicates that one entity possesses, is associated with, or is identified by a specific National Olympic Committee (NOC) code or organization.
-
B.
hasNOCCode
Indicates that an entity is associated with a specific National Occupational Classification (NOC) code that categorizes its occupation or job type.
-
C.
legalStatusAtApproval
Indicates the legal status or classification an entity held at the time it was formally approved.
-
D.
notStatus
Indicates that an entity does not have, is not in, or does not match a specified status or state.
-
E.
NROStatus
Indicates the current state or condition of an entity within the NRO (e.g., whether it is active, inactive, pending, or in another defined status).
- 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_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.