Triple
T511051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-2 rocket |
E10608
|
entity |
| Predicate | maximumRange |
P5433
|
FINISHED |
| Object | approximately 320 km |
—
|
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 320 km | Statement: [V-2 rocket, maximumRange, approximately 320 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRange Context triple: [V-2 rocket, maximumRange, approximately 320 km]
-
A.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
B.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
-
C.
maximumIntensity
Indicates the greatest level or strength that a quantity, effect, or signal can reach within a given context.
-
D.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
E.
rangeCapability
chosen
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f165b91c81908c2d2ba15c64b956 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edfe236481909901cc7d4281b33c |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.