Triple
T15972202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurice Greene |
E387351
|
entity |
| Predicate | personalBest60m |
P120672
|
FINISHED |
| Object | 6.39 s |
—
|
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.39 s | Statement: [Maurice Greene, personalBest60m, 6.39 s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBest60m Context triple: [Maurice Greene, personalBest60m, 6.39 s]
-
A.
personalBestMarathon
Indicates that the associated marathon performance is the best (fastest or highest-achieving) marathon result attained by the person in question.
-
B.
personalBest
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
C.
personalBest5000m
Indicates that the 5000-meter performance referenced is the best (fastest or highest-achieving) result that a person has ever attained at that distance.
-
D.
personalBestMarathonYear
Indicates the year in which an entity achieved their personal best performance in a marathon.
-
E.
personalBest_halfMarathon
Indicates that the associated half marathon performance is the best (fastest or highest-achieving) one recorded for the person.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:54 a.m.