Triple

T34213569
Position Surface form Disambiguated ID Type / Status
Subject R-60 E877723 entity
Predicate minRange P84306 FINISHED
Object approximately 300 m 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 300 m | Statement: [R-60, minRange, approximately 300 m]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: minRange
Context triple: [R-60, minRange, approximately 300 m]
  • A. minimumRange chosen
    Indicates the smallest allowable or observed value within a specified range for a given relationship or measurement.
  • B. minimumSize
    Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
  • C. rangeOf
    Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
  • D. minimumWidth
    Indicates that there is a specified smallest allowable or required width for something in the relationship.
  • E. lowerLimit
    Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
  • 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_69f349b0b4bc819088c1552424089ee9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7107acf0481909b01467b9ebbde01 completed May 3, 2026, 9:08 a.m.
PD Predicate disambiguation batch_69f70f3c5bfc81908585f52e196dafe5 completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 1:55 a.m.