Triple
T9734438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulfur Emission Control Areas |
E236021
|
entity |
| Predicate | complianceVerifiedBy |
P18400
|
FINISHED |
| Object | bunker delivery notes |
—
|
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: bunker delivery notes | Statement: [Sulfur Emission Control Areas, complianceVerifiedBy, bunker delivery notes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complianceVerifiedBy Context triple: [Sulfur Emission Control Areas, complianceVerifiedBy, bunker delivery notes]
-
A.
dataTypeVerified
Indicates that the data’s type has been checked and confirmed to match the expected or required type.
-
B.
providesCompliance
Indicates that one entity supplies or ensures adherence to required rules, standards, or regulations for another entity.
-
C.
indicatesComplianceWith
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
-
D.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
E.
attestedBy
chosen
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
- 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_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. |
Created at: March 30, 2026, 8:22 p.m.