Triple
T34667402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istiophoridae |
E890290
|
entity |
| Predicate | maximumSpeedCharacteristic |
P2096
|
FINISHED |
| Object | among fastest marine fishes |
—
|
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: among fastest marine fishes | Statement: [Istiophoridae, maximumSpeedCharacteristic, among fastest marine fishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSpeedCharacteristic Context triple: [Istiophoridae, maximumSpeedCharacteristic, among fastest marine fishes]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
C.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
D.
maximumCurrentSpeed
Indicates the highest current speed value that an entity is allowed or able to reach under present conditions.
-
E.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
- 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_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 2:05 a.m.