Triple

T28062966
Position Surface form Disambiguated ID Type / Status
Subject Uttarapatha E709164 entity
Predicate directionalMeaning P67274 FINISHED
Object northern route 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: northern route | Statement: [Uttarapatha, directionalMeaning, northern route]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: directionalMeaning
Context triple: [Uttarapatha, directionalMeaning, northern route]
  • A. orientationMeaning
    Indicates the conceptual or semantic interpretation associated with a particular orientation or directional arrangement between entities.
  • B. definesDirection
    Indicates that one entity specifies or establishes the orientation, course, or path along which another entity is directed or proceeds.
  • C. logicalMeaning
    Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
  • D. geographicDirectionImpliedByName chosen
    Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
  • E. directionalRole
    Indicates a role or function defined in terms of a direction or orientation relative to another entity or reference frame.
  • 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_69ef9b6eb6d88190a3fea236eb0f7bed completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f75dc25fa08190b371faf36d9fb72c completed May 3, 2026, 2:37 p.m.
PD Predicate disambiguation batch_69f758586534819083e91172f4bf5098 completed May 3, 2026, 2:14 p.m.
Created at: April 27, 2026, 8:41 p.m.