Triple
T25455166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehachapi Loop |
E637893
|
entity |
| Predicate | hasMinimumRadius |
P84417
|
FINISHED |
| Object | approximately 1,200 feet |
—
|
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 1,200 feet | Statement: [Tehachapi Loop, hasMinimumRadius, approximately 1,200 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinimumRadius Context triple: [Tehachapi Loop, hasMinimumRadius, approximately 1,200 feet]
-
A.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
-
B.
hasRadiusType
Indicates that an entity has a radius characterized by a specific type or classification.
-
C.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
D.
hasMinimum
chosen
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
-
E.
hasCoveringRadius
Indicates the maximum distance from any point in a space to the nearest point in a given set, defining how well that set covers the space.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 2:04 p.m.