Triple
T37593904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MG 34 Panzerlauf |
E935327
|
entity |
| Predicate | hasModificationComparedTo |
P200656
|
FINISHED |
| Object | standard MG 34 |
—
|
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: standard MG 34 | Statement: [MG 34 Panzerlauf, hasModificationComparedTo, standard MG 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModificationComparedTo Context triple: [MG 34 Panzerlauf, hasModificationComparedTo, standard MG 34]
-
A.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
B.
isModifiedAs
Indicates that an entity has been altered or changed from its original state in some specified manner.
-
C.
hasLexicalDifferencesWith
Indicates that two linguistic items differ from each other in their word choice or lexical form.
-
D.
hasComparison
Indicates that one entity is being evaluated or contrasted relative to another entity based on some shared attribute or criterion.
-
E.
isMinorUpdateComparedTo
Indicates that one item represents only a small or incremental change relative to another item.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69ff9d9ba1ac8190a0cca5764bb5904d |
completed | May 9, 2026, 8:48 p.m. |
Created at: May 3, 2026, 4:18 p.m.