Triple
T38657287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosbury Flop |
E939925
|
entity |
| Predicate | firstUsedCompetitivelyBy |
P206606
|
FINISHED |
| Object | Dick Fosbury |
E274877
|
NE 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: Dick Fosbury | Statement: [Fosbury Flop, firstUsedCompetitivelyBy, Dick Fosbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedCompetitivelyBy Context triple: [Fosbury Flop, firstUsedCompetitivelyBy, Dick Fosbury]
-
A.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
B.
firstKnownTournamentYear
Indicates the year in which a tournament was first known to have been held.
-
C.
firstUsedInTournament
Indicates that an entity (such as a move, strategy, or item) was used for the first time in a specific tournament.
-
D.
firstOfficialMatchYear
Indicates the calendar year in which an entity participated in its first official match or game.
-
E.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
- F. None of above. chosen
Provenance (5 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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a420e025bf8819098ee83e1b2e6a3f1 |
completed | June 29, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:33 p.m.