Triple
T16234363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100 metres – Beijing 2008 |
E394065
|
entity |
| Predicate | finalLocalTime |
P21406
|
FINISHED |
| Object | 22:30 |
—
|
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: 22:30 | Statement: [100 metres – Beijing 2008, finalLocalTime, 22:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLocalTime Context triple: [100 metres – Beijing 2008, finalLocalTime, 22:30]
-
A.
localTime
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
-
B.
endTimeLocal
chosen
Indicates the local date and time at which an event, activity, or state concludes.
-
C.
localTimeOf
Indicates the specific local time associated with a given entity, typically relative to its geographic location or time zone.
-
D.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
-
E.
utcTime
Indicates that the associated time value is expressed in Coordinated Universal Time (UTC), independent of local time zones.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2be2f881908ec2483507cb0b00 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.