Triple
T10051671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Walker |
E207761
|
entity |
| Predicate | hasRangeControl |
P70661
|
FINISHED |
| Object | Range operations center |
—
|
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: Range operations center | Statement: [Fort Walker, hasRangeControl, Range operations center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRangeControl Context triple: [Fort Walker, hasRangeControl, Range operations center]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
controlRange
chosen
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
C.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
D.
hasColorRange
Indicates that an entity possesses or is associated with a specific span or set of colors, rather than a single discrete color.
-
E.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf9135bc8190a48a2e5cbafca0cd |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.