Triple
T3597179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 20th Mountain Army |
E76166
|
entity |
| Predicate | usedTerrain |
P20426
|
FINISHED |
| Object | mountainous terrain |
—
|
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: mountainous terrain | Statement: [German 20th Mountain Army, usedTerrain, mountainous terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTerrain Context triple: [German 20th Mountain Army, usedTerrain, mountainous terrain]
-
A.
hasBeginnerTerrain
Indicates that something provides or includes terrain or areas suitable for beginners.
-
B.
hasAdvancedTerrain
Indicates that an entity possesses or is associated with terrain featuring complex, challenging, or enhanced physical characteristics beyond standard ground conditions.
-
C.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
D.
terrainCapability
chosen
Indicates the types of terrain or ground conditions in which an entity can effectively operate or function.
-
E.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc19c71608190a87c98214321214c |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.