Triple

T380634
Position Surface form Disambiguated ID Type / Status
Subject Candidate Recommendation E8669 entity
Predicate timeBoundBy P302 FINISHED
Object implementation period defined by the Working Group 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: implementation period defined by the Working Group | Statement: [Candidate Recommendation, timeBoundBy, implementation period defined by the Working Group]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeBoundBy
Context triple: [Candidate Recommendation, timeBoundBy, implementation period defined by the Working Group]
  • A. timePeriodWithin
    Indicates that one time period is entirely contained within the bounds of another time period.
  • B. timePeriod chosen
    Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
  • C. time
    Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
  • D. commitmentTiming
    Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
  • E. hasDeadline
    Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
  • 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_69a2e7f47dd08190a4e294ccbbe46cd4 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec2c95088190a603bb1ee076ebd6 completed Feb. 28, 2026, 1:22 p.m.
PD Predicate disambiguation batch_69a2e964d4b481909290e474b0341e3c completed Feb. 28, 2026, 1:11 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.