Triple
T11292775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gracie Gold |
E267367
|
entity |
| Predicate | personalBestShortProgramScore |
P98348
|
FINISHED |
| Object | 76.43 |
—
|
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: 76.43 | Statement: [Gracie Gold, personalBestShortProgramScore, 76.43]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBestShortProgramScore Context triple: [Gracie Gold, personalBestShortProgramScore, 76.43]
-
A.
personalBest
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
B.
lowestScore
Indicates that the associated value is the smallest (minimum) score among a set of scores.
-
C.
individualScoring
Indicates that a specific individual receives or is assigned a particular score or evaluation in a given context.
-
D.
personalBest_halfMarathon
Indicates that the associated half marathon performance is the best (fastest or highest-achieving) one recorded for the person.
-
E.
hourRecordDistance
Indicates that one entity holds or represents the record for the greatest distance covered within a one-hour time period relative to another entity or context.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e989fdac81909a4a75f1f68b55c6 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.