Triple
T30678481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ehrwalder Sonnenspitze |
E780982
|
entity |
| Predicate | requiresHeadForHeights |
P196461
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ehrwalder Sonnenspitze, requiresHeadForHeights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresHeadForHeights Context triple: [Ehrwalder Sonnenspitze, requiresHeadForHeights, yes]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
estimatedHeadHeightInMeters
Indicates the estimated vertical height of a person's head, measured in meters.
-
C.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
-
D.
coreHeight
Indicates the vertical size or elevation of the central or main part of an object or structure.
-
E.
hasTraditionalHeaddressHeight
Indicates the relationship between an entity and the measured height of its traditional headdress.
- F. None of above. chosen
Provenance (4 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
| PDg | Predicate description generation | batch_69fe38bc3e9c8190838430b22b82503f |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 29, 2026, 8:32 p.m.