Triple

T230775
Position Surface form Disambiguated ID Type / Status
Subject LHCf E4405 entity
Predicate distanceFromInteractionPoint P7750 FINISHED
Object about 140 meters from ATLAS interaction point 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: about 140 meters from ATLAS interaction point | Statement: [LHCf, distanceFromInteractionPoint, about 140 meters from ATLAS interaction point]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceFromInteractionPoint
Context triple: [LHCf, distanceFromInteractionPoint, about 140 meters from ATLAS interaction point]
  • A. distanceFromTerminus
    Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
  • B. locatedAtInteractionPoint
    Indicates that an entity is positioned at a specific interaction point where interactions or exchanges are intended to occur.
  • C. interactionPoint
    Indicates a specific location or moment where two or more entities come into contact or engage with each other.
  • D. distance chosen
    Indicates the spatial separation or length between two points, objects, or locations.
  • E. distanceCategory
    Indicates the qualitative classification of how far apart two entities are from each other (e.g., near, medium, far).
  • 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_69a257363ffc81909757bde7ab3404da completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25e0868708190ad551ca06cc57f4a completed Feb. 28, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69a25b5a075081909b0e9b88c1492d5a completed Feb. 28, 2026, 3:04 a.m.
Created at: Feb. 28, 2026, 2:53 a.m.