Triple

T21553664
Position Surface form Disambiguated ID Type / Status
Subject Notus E531829 entity
Predicate positionInCardinalDirections P124104 FINISHED
Object south 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: south | Statement: [Notus, positionInCardinalDirections, south]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionInCardinalDirections
Context triple: [Notus, positionInCardinalDirections, south]
  • A. latitudeDirection chosen
    Indicates the cardinal direction (north or south) associated with a given latitude value relative to the equator.
  • B. directionRelativeTo
    Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
  • C. geographicDirectionImpliedByName
    Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
  • D. directionInNorthernHemisphere
    Indicates that the specified direction is defined or measured relative to the orientation of the Northern Hemisphere (e.g., based on its geographic or celestial reference frame).
  • E. directionBy
    Indicates that one entity provides directional guidance, orientation, or navigational reference for 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeb594956c8190a5b4d81911e3927d completed April 27, 2026, 1:02 a.m.
PD Predicate disambiguation batch_69e6320766308190ba5dca2f7c826aa4 completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:29 p.m.