Triple
T2582036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gebirgsjäger division |
E57113
|
entity |
| Predicate | equippedFor |
P40410
|
FINISHED |
| Object | high‑altitude operations |
—
|
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: high‑altitude operations | Statement: [Gebirgsjäger division, equippedFor, high‑altitude operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equippedFor Context triple: [Gebirgsjäger division, equippedFor, high‑altitude operations]
-
A.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
-
B.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
C.
recommendedEquipment
Indicates that one entity suggests or endorses another entity as suitable equipment to be used in a particular context or activity.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
capturedEquipment
Indicates that one party has taken possession of another party’s equipment, typically as a result of conflict, competition, or enforcement.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3c843bc8190837cea3441bf3ca1 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd209d934819093600889af9104c3 |
completed | March 7, 2026, 7:21 a.m. |
Created at: March 6, 2026, 9:49 p.m.