Triple
T24800479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooster Dragon Mountain |
E620508
|
entity |
| Predicate | hasHighestPeakName |
P160072
|
FINISHED |
| Object | Cheonhwangbong |
—
|
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: Cheonhwangbong | Statement: [Rooster Dragon Mountain, hasHighestPeakName, Cheonhwangbong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPeakName Context triple: [Rooster Dragon Mountain, hasHighestPeakName, Cheonhwangbong]
-
A.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
B.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
C.
countryHighestPeak
Indicates that a given peak is the tallest mountain within the specified country.
-
D.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
E.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 4:49 a.m.