Triple
T11462699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MG 34 |
E271699
|
entity |
| Predicate | frontlineUse |
P99707
|
FINISHED |
| Object | infantry machine gun |
—
|
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: infantry machine gun | Statement: [MG 34, frontlineUse, infantry machine gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontlineUse Context triple: [MG 34, frontlineUse, infantry machine gun]
-
A.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
B.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
-
C.
frontLineService
Indicates that an entity provides direct, first-contact service or support to customers, clients, or the public.
-
D.
frontlineRole
Indicates that an entity serves in a primary, direct-contact position at the forefront of an activity, operation, or service.
-
E.
mainFrontlinePeriod
Indicates the time span during which an entity served as the primary or most active presence on the frontline.
- 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_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. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:35 p.m.