Triple
T26489732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Møllehøj |
E669122
|
entity |
| Predicate | previousHighestPointOfDenmarkWas |
P210
|
FINISHED |
| Object | Yding Skovhøj |
—
|
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: Yding Skovhøj | Statement: [Møllehøj, previousHighestPointOfDenmarkWas, Yding Skovhøj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHighestPointOfDenmarkWas Context triple: [Møllehøj, previousHighestPointOfDenmarkWas, Yding Skovhøj]
-
A.
chartPeakDenmark
Indicates that something reached its highest position on a music chart specifically in Denmark.
-
B.
highestPoint
chosen
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
nearHighestPeakOf
Indicates that one entity is located close to the highest peak of another referenced geographic or topographic feature.
-
D.
peakOf
Indicates that one entity represents the highest or most extreme point, level, or intensity within the extent or progression of another entity.
-
E.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 1:02 a.m.