Triple
T19472867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planken |
E487167
|
entity |
| Predicate | hasAlpineLandscape |
P45689
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Planken, hasAlpineLandscape, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlpineLandscape Context triple: [Planken, hasAlpineLandscape, true]
-
A.
hasAlpineFlora
Indicates that an entity possesses or is characterized by plant life typical of high-altitude alpine environments.
-
B.
isAlpineResort
Indicates that the subject is a resort located in, or characteristic of, an alpine (mountainous) region.
-
C.
isAlpineLake
Indicates that a given lake is located in, or characteristic of, an alpine (high-mountain) environment.
-
D.
hasMountainScenery
Indicates that a place or area features views or landscapes dominated by mountains.
-
E.
hasMountainousTerrain
chosen
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633ea604c8190a2feacb709b7ca27 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.