Triple

T18874263
Position Surface form Disambiguated ID Type / Status
Subject UN Regulation No. 83 E461643 entity
Predicate setsRequirementOn P39303 FINISHED
Object pollutant emission limits 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: pollutant emission limits | Statement: [UN Regulation No. 83, setsRequirementOn, pollutant emission limits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: setsRequirementOn
Context triple: [UN Regulation No. 83, setsRequirementOn, pollutant emission limits]
  • A. establishedRequirement chosen
    Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
  • B. requiredTo
    Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
  • C. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • D. basedOnRequirementOf
    Indicates that something is established, created, or determined according to a specified requirement or set of requirements.
  • E. maintenanceRequirement
    Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
  • 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c3cd49748190948d535918aec3de completed April 20, 2026, 6:12 a.m.
PD Predicate disambiguation batch_69e48d22dde8819093b1d963bd673365 completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:57 a.m.