Triple
T38657294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosbury Flop |
E939925
|
entity |
| Predicate | approachPath |
P6174
|
FINISHED |
| Object | curved run-up |
—
|
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: curved run-up | Statement: [Fosbury Flop, approachPath, curved run-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachPath Context triple: [Fosbury Flop, approachPath, curved run-up]
-
A.
approachRoute
chosen
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
B.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
C.
approachLocation
Indicates that an entity moves closer to or heads toward a specified location.
-
D.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
E.
approachOver
Indicates that one entity moves closer to another entity from a position above or higher than 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:33 p.m.