Triple
T7940383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DeLorean time machine |
E184373
|
entity |
| Predicate | requiresSpeed |
P79916
|
FINISHED |
| Object | 88 miles per hour |
—
|
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: 88 miles per hour | Statement: [DeLorean time machine, requiresSpeed, 88 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSpeed Context triple: [DeLorean time machine, requiresSpeed, 88 miles per hour]
-
A.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
B.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
C.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
D.
requiresQuality
Indicates that one entity depends on or needs another entity to possess a specific quality or attribute in order for a condition, action, or relationship to hold.
-
E.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0ac8bc8190b4e4f79b15c316b3 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:08 p.m.