Triple

T20063966
Position Surface form Disambiguated ID Type / Status
Subject space VLBI E499557 entity
Predicate usesBaselineLengthsUpTo P55279 FINISHED
Object hundreds of thousands of kilometers 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: hundreds of thousands of kilometers | Statement: [space VLBI, usesBaselineLengthsUpTo, hundreds of thousands of kilometers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesBaselineLengthsUpTo
Context triple: [space VLBI, usesBaselineLengthsUpTo, hundreds of thousands of kilometers]
  • A. hasBaselineLength
    Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
  • B. usesBaseline chosen
    Indicates that one entity relies on or applies another entity as a reference baseline for comparison, measurement, or evaluation.
  • C. usesMatchLength
    Indicates that one entity applies or enforces the same length or duration as that of a corresponding match or matching element.
  • D. baseLengthOriginal
    Indicates the original or initial length value of a base element before any changes or transformations.
  • E. maximumExtentFromBaseline
    Indicates the greatest distance or deviation of something from a defined baseline reference.
  • 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_69da6276bcf48190aabbf279192a5fb4 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66377b6b48190a0a37279f285123e completed April 20, 2026, 5:33 p.m.
PD Predicate disambiguation batch_69e54cee7a5c819084ae4ff26419833f completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 3:39 p.m.