Triple
T38657292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosbury Flop |
E939925
|
entity |
| Predicate | bodyPositionOverBar |
P132822
|
FINISHED |
| Object | head and shoulders first |
—
|
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: head and shoulders first | Statement: [Fosbury Flop, bodyPositionOverBar, head and shoulders first]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyPositionOverBar Context triple: [Fosbury Flop, bodyPositionOverBar, head and shoulders first]
-
A.
bearerPosition
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
-
B.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
C.
bodyPositionRequirement
chosen
Indicates a required or specified physical posture or orientation of a body that must be met for an action, condition, or relationship to hold.
-
D.
bearerPositionNumber
Indicates the specific ordinal position or slot that a bearer occupies within an ordered set or sequence of bearers.
-
E.
stemPosition
Indicates the relative location or orientation of a stem with respect to another reference point or structure.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.