Triple
T12914104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vergeltungswaffe 2 |
E308931
|
entity |
| Predicate | maximumSpeed_m_per_s |
P2096
|
FINISHED |
| Object | approximately 1700 |
—
|
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 1700 | Statement: [Vergeltungswaffe 2, maximumSpeed_m_per_s, approximately 1700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSpeed_m_per_s Context triple: [Vergeltungswaffe 2, maximumSpeed_m_per_s, approximately 1700]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
C.
maximumWaterSpeed_kmh
Indicates the highest speed, measured in kilometers per hour, at which an entity can move through water.
-
D.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a0d6508190bca9668e9e06abfe |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.