Triple
T33120961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canoe sprint at the 2012 Summer Olympics |
E847593
|
entity |
| Predicate | distanceContested |
P206360
|
FINISHED |
| Object | 200 m |
—
|
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: 200 m | Statement: [canoe sprint at the 2012 Summer Olympics, distanceContested, 200 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceContested Context triple: [canoe sprint at the 2012 Summer Olympics, distanceContested, 200 m]
-
A.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more parties.
-
B.
areContestedIn
Indicates that something is the subject of dispute, challenge, or competition within a particular context, event, or process.
-
C.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
D.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
E.
capitalContested
Indicates that the status of being the capital of a region or country is disputed or claimed by multiple parties.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:27 a.m.