Triple

T868553
Position Surface form Disambiguated ID Type / Status
Subject ISO 8601 E18759 entity
Predicate orderingPrinciple P1803 FINISHED
Object largest time unit to smallest time unit 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: largest time unit to smallest time unit | Statement: [ISO 8601, orderingPrinciple, largest time unit to smallest time unit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orderingPrinciple
Context triple: [ISO 8601, orderingPrinciple, largest time unit to smallest time unit]
  • A. orderedBy
    Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
  • B. selectionOrderAdjustment
    Indicates a modification to the original order in which items or options were selected, such as reordering or adjusting their selection sequence.
  • C. orderPrecedence chosen
    Indicates that one entity must come before another in a defined sequence or priority order.
  • D. originallyOrderedBy
    Indicates that one entity was the initial source or originator of an order or request for another entity.
  • E. order
    Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
  • 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_69a4938ce8688190a24bdfef82ba7d21 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac7f98908190883f71049092c7c8 completed March 1, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69a4aa87504481909618a6815948da6f completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.