Triple
T11462426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großfuß AG |
E271693
|
entity |
| Predicate | MG 42Role |
P88584
|
FINISHED |
| Object | primary designer |
—
|
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: primary designer | Statement: [Großfuß AG, MG 42Role, primary designer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MG 42Role Context triple: [Großfuß AG, MG 42Role, primary designer]
-
A.
Berdan No.1 rifle
Indicates that an entity is a Berdan No.1 rifle, i.e., it has the identity or classification of that specific rifle model.
-
B.
Me 262Role
Indicates the functional role or operational use assigned to the Me 262 aircraft (e.g., fighter, bomber, reconnaissance).
-
C.
mainGunModel
chosen
Indicates the specific model or type designation of the primary gun or main weapon system used by an entity.
-
D.
SM.79Role
Indicates the functional role or operational use associated with the SM.79 entity (e.g., bomber, transport, trainer).
-
E.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
- 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_69d822f384f08190b1150ed1389dd31a |
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.