Triple
T4953897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euripus Strait |
E111233
|
entity |
| Predicate | hasMaximumCurrentSpeed |
P2096
|
FINISHED |
| Object | up to about 8 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: up to about 8 knots | Statement: [Euripus Strait, hasMaximumCurrentSpeed, up to about 8 knots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumCurrentSpeed Context triple: [Euripus Strait, hasMaximumCurrentSpeed, up to about 8 knots]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
C.
supportsMaximumCurrent
Indicates that one entity is capable of handling or allowing a specified maximum electric current for another entity or connection.
-
D.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
E.
hasMaximumEfficiencyAt
Indicates that an entity reaches or exhibits its highest possible efficiency under a specified condition, context, or parameter value.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b82dd88190adfb08c3b3191fe0 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.