Triple
T34667647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istiophorus |
E890296
|
entity |
| Predicate | maximumRecordedSpeed |
P58444
|
FINISHED |
| Object | approximately 110 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: approximately 110 km/h | Statement: [Istiophorus, maximumRecordedSpeed, approximately 110 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRecordedSpeed Context triple: [Istiophorus, maximumRecordedSpeed, approximately 110 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.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
maximumCurrentSpeed
Indicates the highest current speed value that an entity is allowed or able to reach under present conditions.
-
D.
topSpeedRecordYear
Indicates the year in which an entity achieved its highest recorded top speed.
-
E.
maximumBusSpeed
Indicates the highest speed that a bus is allowed or able to travel 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 2:05 a.m.