Triple
T20322111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-400 missile system |
E492230
|
entity |
| Predicate | maximumEngagementRange_km |
P61967
|
FINISHED |
| Object | up to 400 |
—
|
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: up to 400 | Statement: [S-400 missile system, maximumEngagementRange_km, up to 400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumEngagementRange_km Context triple: [S-400 missile system, maximumEngagementRange_km, up to 400]
-
A.
engagementRange
chosen
Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
-
B.
maximumRangeNauticalMiles
Indicates the greatest distance, measured in nautical miles, that something can travel or operate under specified conditions.
-
C.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
D.
chargeRadius
Indicates the characteristic radial distance around an entity within which its electric charge or charge-related influence is considered effective.
-
E.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.