Triple
T1573328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Air Warfare Center Weapons Division |
E33590
|
entity |
| Predicate | hasTestRangeType |
P8771
|
FINISHED |
| Object | land ranges |
—
|
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: land ranges | Statement: [Naval Air Warfare Center Weapons Division, hasTestRangeType, land ranges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTestRangeType Context triple: [Naval Air Warfare Center Weapons Division, hasTestRangeType, land ranges]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
C.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
D.
rangeType
chosen
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
E.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.