Triple
T29603235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bravo-16 range |
E754506
|
entity |
| Predicate | rangeComplex |
P167498
|
FINISHED |
| Object | Fallon Range Training Complex |
—
|
NE NERFINISHED |
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: Fallon Range Training Complex | Statement: [Bravo-16 range, rangeComplex, Fallon Range Training Complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeComplex Context triple: [Bravo-16 range, rangeComplex, Fallon Range Training Complex]
-
A.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
-
B.
rangeExpansion
Indicates an increase in the spatial or contextual extent over which something applies, operates, or is distributed.
-
C.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
D.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
E.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
- F. None of above. chosen
Provenance (4 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66de515a88190aa297e74cb541501 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:23 p.m.