Triple
T37370871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturmtiger |
E927837
|
entity |
| Predicate | designedToFireFrom |
P200061
|
FINISHED |
| Object | short range |
—
|
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: short range | Statement: [Sturmtiger, designedToFireFrom, short range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToFireFrom Context triple: [Sturmtiger, designedToFireFrom, short range]
-
A.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
-
B.
designedForFirearm
Indicates that something is specifically created or intended to be used with a firearm.
-
C.
designedToFire
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
D.
hasFireOnTheMoveCapability
Indicates that an entity is capable of continuing to move while simultaneously delivering effective fire or engaging targets.
-
E.
muzzleType
Indicates the specific style or configuration of a muzzle associated with an entity, such as a weapon or animal.
- F. None of above. chosen
Provenance (4 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
| PDg | Predicate description generation | batch_69ff6eefa9c48190aac36916990f6db5 |
completed | May 9, 2026, 5:29 p.m. |
Created at: May 3, 2026, 4:16 p.m.