Triple
T20379554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pete |
E497785
|
entity |
| Predicate | maximumSpeedAchieved_kmh |
P12248
|
FINISHED |
| Object | 7274 |
—
|
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: 7274 | Statement: [Pete, maximumSpeedAchieved_kmh, 7274]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSpeedAchieved_kmh Context triple: [Pete, maximumSpeedAchieved_kmh, 7274]
-
A.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
speedAchieved
chosen
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
D.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
E.
maximumWaterSpeed_kmh
Indicates the highest speed, measured in kilometers per hour, at which an entity can move through water.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678af651c8190b4922294a937e699 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.