Triple
T29021884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLaren F1 |
E737470
|
entity |
| Predicate | topSpeedRecordSpeed |
P58444
|
FINISHED |
| Object | 240.1 mph |
—
|
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: 240.1 mph | Statement: [McLaren F1, topSpeedRecordSpeed, 240.1 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topSpeedRecordSpeed Context triple: [McLaren F1, topSpeedRecordSpeed, 240.1 mph]
-
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.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
peacetimeSpeedRecord
Indicates the maximum speed achieved under non-combat, peacetime conditions, recognized as a record.
-
E.
worldSpeedRecordCountry
Indicates the country in which a given world speed record was achieved or is held.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66005ea00819085501231fe82cc5e |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:49 a.m.