Triple
T18459068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katelyn Ohashi |
E450982
|
entity |
| Predicate | achievedPerfect10On |
P131729
|
FINISHED |
| Object | floor exercise |
—
|
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: floor exercise | Statement: [Katelyn Ohashi, achievedPerfect10On, floor exercise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedPerfect10On Context triple: [Katelyn Ohashi, achievedPerfect10On, floor exercise]
-
A.
scored100PointsInAGame
Indicates that an entity achieved a total of 100 points in a single game or match.
-
B.
achievedPodiumIn
Indicates that an entity finished in a top-ranked (podium) position in a specified competition or event.
-
C.
scored100PointSeason
Indicates that an entity (typically an athlete) completed a season in which they scored at least 100 points.
-
D.
notableChartAchievement
Indicates that an entity has achieved a significant or distinguished position or milestone on a recognized ranking or performance chart.
-
E.
firstToAchieve
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
- F. None of above. chosen
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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7cdb5c8190a399f0e4052f7d1f |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:33 a.m.