Triple

T35690700
Position Surface form Disambiguated ID Type / Status
Subject Anoat system E1031279 entity
Predicate proximityToEvent P45864 FINISHED
Object Battle of Hoth NE NERFINISHED

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: Battle of Hoth | Statement: [Anoat system, proximityToEvent, Battle of Hoth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: proximityToEvent
Context triple: [Anoat system, proximityToEvent, Battle of Hoth]
  • A. hasNearbyEvent chosen
    Indicates that an event occurs close in space or time to the referenced entity.
  • B. proximityToLandmark
    Indicates a spatial relationship where one entity is located near or close to a specified landmark.
  • C. hasNearbyEventType
    Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
  • D. isCloseTo
    Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
  • E. closerTo
    Indicates that one entity is at a smaller distance to a reference entity than another entity is.
  • 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_69f76e0c73ec819080ab60a9e2f5f1f6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a34f8ee08190a040304635539a8f completed May 3, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69f7a06f125c8190843af194f042a465 completed May 3, 2026, 7:22 p.m.
Created at: May 3, 2026, 4:05 p.m.