Triple
T16234384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100 metres – Beijing 2008 |
E394065
|
entity |
| Predicate | windInFinal |
P60166
|
FINISHED |
| Object | +0.0 m/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: +0.0 m/s | Statement: [100 metres – Beijing 2008, windInFinal, +0.0 m/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windInFinal Context triple: [100 metres – Beijing 2008, windInFinal, +0.0 m/s]
-
A.
windSpeed
chosen
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
B.
windCharacteristics
Indicates the specific properties or qualities that describe the behavior and nature of the wind in a given context.
-
C.
windResource
Indicates the availability, quality, or characteristics of wind at a location as a usable energy resource.
-
D.
blowsAcross
Indicates that something (typically wind, air, or a current) moves across or over another entity or area, passing from one side or region to another.
-
E.
windDirectionAtLandfall
Indicates the direction from which the wind is blowing at the moment and location where a storm makes landfall.
- 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.