Triple
T525905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Olympic Committee retrospective medal assignments |
E10917
|
entity |
| Predicate | standardizedAward |
P1619
|
FINISHED |
| Object | gold medal |
—
|
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: gold medal | Statement: [International Olympic Committee retrospective medal assignments, standardizedAward, gold medal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedAward Context triple: [International Olympic Committee retrospective medal assignments, standardizedAward, gold medal]
-
A.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
B.
awardType
chosen
Indicates the specific category or kind of award associated with an entity or event.
-
C.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
D.
awardClass
Indicates the classification or category assigned to an award within an award-giving system.
-
E.
relatedAward
Indicates that there is an award connected or associated with the subject entity, such as an honor, prize, or recognition related to it.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b7f448819087e5e7f3b37d7142 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.