Triple

T30080516
Position Surface form Disambiguated ID Type / Status
Subject 18 (deluxe edition) E764442 entity
Predicate hasTrackCountRelation P1707 FINISHED
Object more tracks than Glory (standard edition) 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: more tracks than Glory (standard edition) | Statement: [18 (deluxe edition), hasTrackCountRelation, more tracks than Glory (standard edition)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrackCountRelation
Context triple: [18 (deluxe edition), hasTrackCountRelation, more tracks than Glory (standard edition)]
  • A. hasTrack
    Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
  • B. numberOfTracks chosen
    Indicates the quantity of tracks associated with a given entity.
  • C. hasTrackSequenceConcept
    Indicates that one entity is associated with a conceptual representation of the ordered sequence of tracks or track elements related to it.
  • D. hasTrackSection
    Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
  • E. containsTrackType
    Indicates that one entity includes or is associated with a specific type or category of track.
  • 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_69f22472eee081909791dc372aa766e9 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe59d11e9881909d2f33b7c717030e completed May 8, 2026, 9:46 p.m.
PD Predicate disambiguation batch_69fe394fdfbc8190a931926ae3635cbf completed May 8, 2026, 7:28 p.m.
Created at: April 29, 2026, 7:02 p.m.