Triple
T38657291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosbury Flop |
E939925
|
entity |
| Predicate | orientationRelativeToBar |
P135190
|
FINISHED |
| Object | back to the bar |
—
|
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: back to the bar | Statement: [Fosbury Flop, orientationRelativeToBar, back to the bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationRelativeToBar Context triple: [Fosbury Flop, orientationRelativeToBar, back to the bar]
-
A.
locationOrientation
chosen
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
-
B.
orientationComparedToBA
Indicates how the orientation of one entity is positioned or directed relative to entity B and entity A.
-
C.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
D.
armOrientation
Indicates the spatial direction or angle at which an arm is positioned relative to a reference frame or body.
-
E.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
- 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.