Triple
T23179002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Dumbleyung |
E579098
|
entity |
| Predicate | maximumSpeedRecordSet |
P58444
|
FINISHED |
| Object | 444.71 km/h |
—
|
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: 444.71 km/h | Statement: [Lake Dumbleyung, maximumSpeedRecordSet, 444.71 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSpeedRecordSet Context triple: [Lake Dumbleyung, maximumSpeedRecordSet, 444.71 km/h]
-
A.
maximumSpeedRecord
chosen
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
B.
worldSpeedRecordContext
Indicates the contextual circumstances (such as event, conditions, or category) under which a world speed record is set or recognized.
-
C.
peacetimeSpeedRecord
Indicates the maximum speed achieved under non-combat, peacetime conditions, recognized as a record.
-
D.
worldSpeedRecordLocation
Indicates the location where a world speed record was achieved or officially recorded.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f6dad948190a64f80f2c9e8e4cb |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:04 p.m.