Triple
T25407407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men's discus throw at the 1952 Summer Olympics |
E636595
|
entity |
| Predicate | throwingImplement |
P158273
|
FINISHED |
| Object | men's discus |
—
|
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: men's discus | Statement: [men's discus throw at the 1952 Summer Olympics, throwingImplement, men's discus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throwingImplement Context triple: [men's discus throw at the 1952 Summer Olympics, throwingImplement, men's discus]
-
A.
throwingHand
Indicates which hand (left or right) an entity primarily uses to throw.
-
B.
throws
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
C.
wasThrownFrom
Indicates that an entity was propelled away or ejected from another entity, typically by a forceful or intentional throwing action.
-
D.
downthrowSide
Indicates the side of a fault or geological structure on which the rock mass has moved downward relative to the opposite side.
-
E.
throwsStyle
Indicates that one entity performs a throwing action using a particular style, technique, or manner.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00b10308190a7029652f6921e5d |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:52 p.m.