Triple
T8337393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenzspitze |
E195821
|
entity |
| Predicate | hasSharpRidges |
P59759
|
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: [Lenzspitze, hasSharpRidges, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSharpRidges Context triple: [Lenzspitze, hasSharpRidges, true]
-
A.
hasRidges
chosen
Indicates that one entity possesses raised, linear or patterned ridges on its surface or structure in relation to another entity or context.
-
B.
isRidge
Indicates that something has the form or function of a ridge, typically being a long, narrow raised or elevated feature relative to its surroundings.
-
C.
hasCliffsOn
Indicates that one entity possesses or features cliffs located along or on the surface of another entity.
-
D.
hasRockyTerrain
Indicates that the subject possesses or is characterized by rough, uneven, or rock-covered ground or surface conditions.
-
E.
hasCliffs
Indicates that something possesses or is characterized by the presence of cliffs.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd5027c81909724f25aa30bbe58 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:57 p.m.