Triple

T22695181
Position Surface form Disambiguated ID Type / Status
Subject INGRID E561155 entity
Predicate baselineToFarDetector P116262 FINISHED
Object approximately 295 km 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: approximately 295 km | Statement: [INGRID, baselineToFarDetector, approximately 295 km]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: baselineToFarDetector
Context triple: [INGRID, baselineToFarDetector, approximately 295 km]
  • A. distanceToFarDetector chosen
    Indicates the measured or calculated distance from a given entity to the designated far detector.
  • B. farDetectorLocation
    Indicates that one entity is located at or corresponds to the position of a far (distant) detector relative to another reference point or system.
  • C. hasFarDetector
    Indicates that an entity is equipped with or associated with a detector positioned at a relatively large distance from a reference point or source.
  • D. farDetectorState
    Indicates the operational status or condition of a detector that is located at a distant or remote position relative to a reference point.
  • E. hasFarDetectorFunction
    Indicates that an entity possesses a function or capability specifically related to detecting objects, signals, or phenomena at a long or extended distance.
  • 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_69e2454e615481909c177440be559d2c completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1789d46c881908176bc8e26f366f6 completed April 29, 2026, 3:18 a.m.
PD Predicate disambiguation batch_69ee62b2259c819091ed1387a748b9f3 completed April 26, 2026, 7:08 p.m.
Created at: April 17, 2026, 3:14 p.m.