Triple
T26557303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heeresgebirgsschule Fulpmes |
E666144
|
entity |
| Predicate | terrainTypeOfTrainingArea |
P9701
|
FINISHED |
| Object | Alps |
—
|
NE NERFINISHED |
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: Alps | Statement: [Heeresgebirgsschule Fulpmes, terrainTypeOfTrainingArea, Alps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainTypeOfTrainingArea Context triple: [Heeresgebirgsschule Fulpmes, terrainTypeOfTrainingArea, Alps]
-
A.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
B.
landscapeType
chosen
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
-
C.
terrainSpecialization
Indicates a relationship where an entity is particularly adapted or optimized for operation, performance, or use within a specific type of terrain.
-
D.
hasBeginnerTerrain
Indicates that something provides or includes terrain or areas suitable for beginners.
-
E.
hasPrimaryTerrain
Indicates that an entity’s main or dominant type of terrain or land surface is a specified terrain category.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6146709fc81909851677f0cd4e2d7 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:50 a.m.