Triple

T29115706
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Nedao E737038 entity
Predicate approximateLocationCertainty P134246 FINISHED
Object disputed 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: disputed | Statement: [Battle of the Nedao, approximateLocationCertainty, disputed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateLocationCertainty
Context triple: [Battle of the Nedao, approximateLocationCertainty, disputed]
  • A. hasApproximateLocation
    Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
  • B. exactLocationKnown
    Indicates that the precise geographic or spatial position of an entity is known and specified.
  • C. geographicalCertainty chosen
    Indicates the degree of confidence or precision with which a location or geographic reference is known, specified, or assigned in the relationship.
  • D. positionOnCertainty
    Indicates the degree or stance of confidence, doubt, or certainty an entity has regarding a particular proposition or situation.
  • E. hasUncertainDistance
    Indicates that the distance between two entities is not known precisely or cannot be determined with certainty.
  • 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_69f077ed54e08190bb02a744e8121a66 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69fd592e48cc81909d754cc6c4bd99ae completed May 8, 2026, 3:31 a.m.
PD Predicate disambiguation batch_69fd58b7f9b881909dc099b28d567784 completed May 8, 2026, 3:30 a.m.
Created at: April 28, 2026, 11:22 a.m.