Triple
T9734457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulfur Emission Control Areas |
E236021
|
entity |
| Predicate | requiresFromShipOperators |
P90716
|
FINISHED |
| Object | fuel changeover procedures before entry |
—
|
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: fuel changeover procedures before entry | Statement: [Sulfur Emission Control Areas, requiresFromShipOperators, fuel changeover procedures before entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFromShipOperators Context triple: [Sulfur Emission Control Areas, requiresFromShipOperators, fuel changeover procedures before entry]
-
A.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
B.
crewRequired
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
-
C.
shipyardOperator
Indicates that one entity operates, manages, or runs the shipyard associated with another entity.
-
D.
organizedShip
Indicates that an entity arranged, managed, or coordinated the operation or voyage of a ship.
-
E.
shipsWith
Indicates that one entity is delivered, packaged, or provided together with another entity as part of the same shipment or bundle.
- F. None of above. chosen
Provenance (4 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eebcec08190a9d4606fd26f2e19 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd07c5c978819084abc7267a5ced80 |
completed | April 1, 2026, 11:55 a.m. |
Created at: March 30, 2026, 8:22 p.m.