Triple
T38657296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosbury Flop |
E939925
|
entity |
| Predicate | replacedTechnique |
P30993
|
FINISHED |
| Object | straddle technique |
—
|
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: straddle technique | Statement: [Fosbury Flop, replacedTechnique, straddle technique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedTechnique Context triple: [Fosbury Flop, replacedTechnique, straddle technique]
-
A.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
B.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacesInPractice
chosen
Indicates that one entity has effectively taken over the role, function, or use of another entity in real-world application or usage.
-
D.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
-
E.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
- 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_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 3, 2026, 4:33 p.m.