Triple

T5167230
Position Surface form Disambiguated ID Type / Status
Subject OpenGL E116587 entity
Predicate usesCoordinateSystem P2054 FINISHED
Object right-handed by convention 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: right-handed by convention | Statement: [OpenGL, usesCoordinateSystem, right-handed by convention]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCoordinateSystem
Context triple: [OpenGL, usesCoordinateSystem, right-handed by convention]
  • A. coordinateSystem chosen
    Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
  • B. formsCoordinateCollegeSystemWith
    Indicates that two educational institutions jointly participate in and operate as parts of a shared, coordinated college system.
  • C. hasCoordinates
    Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
  • D. hasCoordinateRole
    Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
  • E. hasSummitCoordinateSystem
    Indicates that a summit or peak is associated with a specific coordinate system used to define its geographic position.
  • 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_69bd445ff97c81909a2615cc56235470 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd792c5ea88190b6aa0e519c744155 completed March 20, 2026, 4:43 p.m.
PD Predicate disambiguation batch_69bd77b36c008190b91011a9fa52b3d2 completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:45 p.m.