Triple
T25145976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yvette Williams |
E629932
|
entity |
| Predicate | personalBestLongJump |
P143653
|
FINISHED |
| Object | 6.28 metres |
—
|
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: 6.28 metres | Statement: [Yvette Williams, personalBestLongJump, 6.28 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBestLongJump Context triple: [Yvette Williams, personalBestLongJump, 6.28 metres]
-
A.
personalBestLongJumpMetres
chosen
Indicates the greatest distance, measured in metres, that an individual has ever achieved in a long jump.
-
B.
setPersonalBestLongJumpYear
Indicates the year in which an entity achieved its personal best performance in the long jump event.
-
C.
personalBest
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
D.
personalBest800m
Indicates that an entity holds or represents a person's best performance or fastest recorded time in the 800-meter event.
-
E.
personalBestMarathon
Indicates that the associated marathon performance is the best (fastest or highest-achieving) marathon result attained by the person in question.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 18, 2026, 6:30 a.m.