Triple
T34795856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick Quax |
E1003076
|
entity |
| Predicate | worldRecordTime5000m |
P79755
|
FINISHED |
| Object | 13:12.9 |
—
|
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: 13:12.9 | Statement: [Dick Quax, worldRecordTime5000m, 13:12.9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRecordTime5000m Context triple: [Dick Quax, worldRecordTime5000m, 13:12.9]
-
A.
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.
-
B.
worldRecord1500mDate
Indicates the date on which a world record was set in the 1500-meter event.
-
C.
worldRecord1500mSurpassedBy
Indicates that a previously held world record in the 1500-meter event has been surpassed by another performance or record.
-
D.
worldRecordTime
chosen
Indicates that an entity’s recorded time for an event is the fastest ever achieved globally, i.e., the official world record time for that event.
-
E.
longDistanceRecordTime
Indicates the time value associated with a long-distance record performance or achievement.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 3:59 p.m.