Triple
T11462662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitler’s buzzsaw |
E271698
|
entity |
| Predicate | weaponFeatureHighlighted |
P76424
|
FINISHED |
| Object | quick-change barrel system |
—
|
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: quick-change barrel system | Statement: [Hitler’s buzzsaw, weaponFeatureHighlighted, quick-change barrel system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponFeatureHighlighted Context triple: [Hitler’s buzzsaw, weaponFeatureHighlighted, quick-change barrel system]
-
A.
weaponFeature
chosen
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
B.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
C.
greaterArmsFeature
Indicates that one entity possesses a more prominent or advanced arm-related feature than another entity.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
armorFeature
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f488248190b9f603cd31c72174 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.