Triple
T38657288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosbury Flop |
E939925
|
entity |
| Predicate | firstMajorUseEvent |
P81076
|
FINISHED |
| Object | 1968 Summer Olympics |
E52656
|
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: 1968 Summer Olympics | Statement: [Fosbury Flop, firstMajorUseEvent, 1968 Summer Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorUseEvent Context triple: [Fosbury Flop, firstMajorUseEvent, 1968 Summer Olympics]
-
A.
firstMajorEventAt
Indicates that the referenced event is the earliest major event associated with the given entity, specifying when that first significant occurrence takes place.
-
B.
firstMajorEventYear
Indicates the calendar year in which the entity’s first major event occurred.
-
C.
firstMajorUseYear
chosen
Indicates the calendar year in which something was first put into major or primary use.
-
D.
firstMajorDevelopment
Indicates that the object is the earliest significant development, milestone, or major advancement associated with the subject.
-
E.
firstMajorInternationalEvent
Indicates that the event is the earliest significant international-level occurrence in which the entity participated or was involved.
- F. None of above.
Provenance (4 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd634fa88190b1debc75a1309c80 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.