Triple
T38657309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosbury Flop |
E939925
|
entity |
| Predicate | safetyDependence |
P103131
|
FINISHED |
| Object | availability of foam landing pits |
—
|
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: availability of foam landing pits | Statement: [Fosbury Flop, safetyDependence, availability of foam landing pits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyDependence Context triple: [Fosbury Flop, safetyDependence, availability of foam landing pits]
-
A.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
B.
safetyRelevant
Indicates that the associated entity, condition, or information has a direct impact on safety or is critical for preventing harm or accidents.
-
C.
safetyContext
Indicates the circumstances, conditions, or environment that affect how safe an action, object, or situation is.
-
D.
safetyRationale
Indicates the reasoning or justification provided to explain how and why something is considered safe or made safe.
-
E.
safetyImplication
chosen
Indicates that one entity has a consequence, effect, or relevance for the safety or risk level associated with another entity or situation.
- 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_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.