Triple

T32055368
Position Surface form Disambiguated ID Type / Status
Subject SECA E818603 entity
Predicate hasStricterStandardsThan P90714 FINISHED
Object global sulfur cap for marine fuels 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: global sulfur cap for marine fuels | Statement: [SECA, hasStricterStandardsThan, global sulfur cap for marine fuels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStricterStandardsThan
Context triple: [SECA, hasStricterStandardsThan, global sulfur cap for marine fuels]
  • A. hasStricterStandardThan chosen
    Indicates that one entity’s rules, criteria, or requirements are more demanding or rigorous than those of another entity.
  • B. isStandardOf
    Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
  • C. requiresStricterRegulationsThan
    Indicates that one entity must be governed by more stringent or demanding regulations than another entity.
  • D. isLessStandardizedThan
    Indicates that one entity follows fewer or less rigid standards, norms, or formalized procedures than another entity.
  • E. standardsUsedIn
    Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
  • 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_69f348fdacec8190b9f74375ca3b2094 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fee0b2da3c8190a3519d0564f2f32d completed May 9, 2026, 7:22 a.m.
PD Predicate disambiguation batch_69fee05b315c819081dfcbfb15273487 completed May 9, 2026, 7:20 a.m.
Created at: May 1, 2026, 12:21 a.m.