Triple

T32817712
Position Surface form Disambiguated ID Type / Status
Subject Eleven (band catalogue) E839344 entity
Predicate hasCanonicalOrdering P198604 FINISHED
Object chronological by release date 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: chronological by release date | Statement: [Eleven (band catalogue), hasCanonicalOrdering, chronological by release date]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCanonicalOrdering
Context triple: [Eleven (band catalogue), hasCanonicalOrdering, chronological by release date]
  • A. hasOrderingMethod
    Indicates that there is a specific method or procedure used to place or arrange an order for something.
  • B. hasElementOrder
    Indicates that one entity is ordered or ranked relative to another within a sequence or hierarchy.
  • C. hasCanonicalOrderWithinOrganon
    Indicates that one element occupies a specific, authoritative sequence position within the structured whole referred to as the Organon.
  • D. hasCanonicalStructure
    Indicates that an entity conforms to or is associated with a standard, officially recognized structural form.
  • E. hasOrderlinessProperty
    Indicates that something possesses a characteristic related to order, organization, or structured arrangement.
  • F. None of above. chosen

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_69f3493df9008190a8f5d843dcd77704 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fef5cf8da881908260ec633830375d completed May 9, 2026, 8:52 a.m.
PD Predicate disambiguation batch_69fef455e40481909861c82007b79bc0 completed May 9, 2026, 8:46 a.m.
PDg Predicate description generation batch_69fef5cec8208190b85665ab6a511a08 completed May 9, 2026, 8:52 a.m.
Created at: May 1, 2026, 1:15 a.m.