Triple

T25723363
Position Surface form Disambiguated ID Type / Status
Subject 09R/27L E645048 entity
Predicate hasOppositeDirection P116628 FINISHED
Object 270DegreesMagneticApprox 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: 270DegreesMagneticApprox | Statement: [09R/27L, hasOppositeDirection, 270DegreesMagneticApprox]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOppositeDirection
Context triple: [09R/27L, hasOppositeDirection, 270DegreesMagneticApprox]
  • A. hasOppositeDirectionTo chosen
    Indicates that one entity’s direction is exactly reversed or opposed to the direction of another entity.
  • B. hasOppositeComponent
    Indicates that one component is related to another as its opposite or contrasting counterpart within a system or structure.
  • C. hasOppositeTime
    Indicates a temporal relationship where one time point or period is positioned as the direct opposite or inverse of another within a defined temporal framework (e.g., day vs. night, past vs. future).
  • D. hasOppositeStatus
    Indicates that two entities hold directly contrasting or mutually exclusive statuses within a given context.
  • E. hasOppositeStructure
    Indicates that one entity possesses a structure that is the inverse or opposite in form, arrangement, or organization relative to another entity.
  • 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_69e77e8476fc8190bd5e9d05b89fad0a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 21, 2026, 10:07 p.m.