Triple
T33007005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLdN RoRo |
E844529
|
entity |
| Predicate | hasRegulatoryCompliance |
P34675
|
FINISHED |
| Object | IMO regulations |
E211018
|
NE 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: IMO regulations | Statement: [CLdN RoRo, hasRegulatoryCompliance, IMO regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulatoryCompliance Context triple: [CLdN RoRo, hasRegulatoryCompliance, IMO regulations]
-
A.
hasRegulations
chosen
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
B.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
C.
regulatesComplianceWith
Indicates that one entity oversees, enforces, or sets rules to ensure another entity adheres to specified standards, laws, or requirements.
-
D.
hasRegulatoryApproval
Indicates that an entity has received formal authorization or clearance from a relevant regulatory authority to operate, be sold, or be used in a specified context.
-
E.
appliesRegulatoryStandard
Indicates that one entity enforces or uses a specific regulatory standard in relation to another entity or context.
- F. None of above.
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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0332a08b48819094aaed6e04a36886 |
completed | May 12, 2026, 2:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34dacec4b081909ff2bd7951a9c541 |
completed | June 19, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a0331998a688190b5d919697d4231ac |
completed | May 12, 2026, 1:56 p.m. |
Created at: May 1, 2026, 1:23 a.m.