Triple
T19340428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saanen Airport |
E483739
|
entity |
| Predicate | terrainEnvironment |
P101500
|
FINISHED |
| Object | mountainous |
—
|
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 | Statement: [Saanen Airport, terrainEnvironment, mountainous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainEnvironment Context triple: [Saanen Airport, terrainEnvironment, mountainous]
-
A.
tourEnvironment
Indicates that an entity conducts or participates in a tour within a particular environment or setting.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
terrainStyle
chosen
Indicates the characteristic type or pattern of terrain associated with an entity or location.
-
D.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
E.
terrainNavigation
Indicates the ability or process of moving through, over, or across different types of terrain or ground conditions.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61856c0948190a3166b3bf3810e43 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.