Triple
T29767356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aframax |
E753950
|
entity |
| Predicate | hasTypicalServiceSpeed |
P56946
|
FINISHED |
| Object | 13–15 knots |
—
|
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: 13–15 knots | Statement: [Aframax, hasTypicalServiceSpeed, 13–15 knots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalServiceSpeed Context triple: [Aframax, hasTypicalServiceSpeed, 13–15 knots]
-
A.
hasServiceSpeed
chosen
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
B.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
C.
serviceSpeedRelativeToLocal
Indicates how the speed or promptness of a service compares to the typical or average service speed in the local area.
-
D.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
E.
requiresSpeed
Indicates that an entity needs to be performed, operated, or handled at or above a certain speed in order to be valid or effective.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 28, 2026, 8:39 p.m.