Triple

T1161193
Position Surface form Disambiguated ID Type / Status
Subject Inner Tracking System E24493 entity
Predicate locatedAtRadius P23277 FINISHED
Object few centimeters to tens of centimeters from beam line 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: few centimeters to tens of centimeters from beam line | Statement: [Inner Tracking System, locatedAtRadius, few centimeters to tens of centimeters from beam line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedAtRadius
Context triple: [Inner Tracking System, locatedAtRadius, few centimeters to tens of centimeters from beam line]
  • A. locatedAlong
    Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
  • B. locatedIn
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • C. radarLocation
    Indicates the geographic position where a radar system is installed or operating.
  • D. approximateRadius chosen
    Indicates that one entity specifies or provides an estimated value for the radius of another entity.
  • E. locatedAtInteractionPoint
    Indicates that an entity is positioned at a specific interaction point where interactions or exchanges are intended to occur.
  • 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_69a494060e148190abb42f971242c197 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcb1915081908834ced85d09e299 completed March 1, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69a4bb525b648190adcb7a29256d3c41 completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:45 p.m.