Triple
T27326962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qu Yunxia |
E689677
|
entity |
| Predicate | worldRecord1500mDate |
P175223
|
FINISHED |
| Object | 1993-09-11 |
—
|
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: 1993-09-11 | Statement: [Qu Yunxia, worldRecord1500mDate, 1993-09-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRecord1500mDate Context triple: [Qu Yunxia, worldRecord1500mDate, 1993-09-11]
-
A.
worldRecordTime
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.
longDistanceRecordDate
Indicates the date on which a long-distance record (such as for travel, communication, or performance over a long distance) was achieved or officially recorded.
-
C.
worldRecordEndDate
Indicates the date on which a particular world record ceased to be valid or was superseded.
-
D.
worldRecordSet
Indicates that an entity has achieved and established the best performance ever recorded in the world for a particular activity, event, or measurable criterion.
-
E.
worldRecordEvent
Indicates that an event involves the setting, holding, or recognition of a world record.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 27, 2026, 11:36 a.m.