Triple
T27326961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qu Yunxia |
E689677
|
entity |
| Predicate | worldRecordTime1500m |
P79755
|
FINISHED |
| Object | 3:50.46 |
—
|
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: 3:50.46 | Statement: [Qu Yunxia, worldRecordTime1500m, 3:50.46]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRecordTime1500m Context triple: [Qu Yunxia, worldRecordTime1500m, 3:50.46]
-
A.
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.
-
B.
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.
-
C.
longDistanceRecordTime
Indicates the time value associated with a long-distance record performance or achievement.
-
D.
recordHolderMen
Indicates that the subject is the male athlete who holds the record for a specified event or category.
-
E.
heldWorldRecordTime
Indicates that an entity achieved and maintained the fastest known performance time in a specific event or activity, recognized as the official world record for a period.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 11:36 a.m.