Triple
T24800480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooster Dragon Mountain |
E620508
|
entity |
| Predicate | hasHighestPeakElevation_m |
P141432
|
FINISHED |
| Object | 845 |
—
|
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: 845 | Statement: [Rooster Dragon Mountain, hasHighestPeakElevation_m, 845]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPeakElevation_m Context triple: [Rooster Dragon Mountain, hasHighestPeakElevation_m, 845]
-
A.
hasHighestElevationsOf
Indicates that one entity possesses the greatest elevation values (e.g., altitudes or heights) compared to another entity or set of entities.
-
B.
hasMainPeakElevation_m
chosen
Indicates the relationship that specifies the elevation, in meters, of the main or highest peak associated with an entity.
-
C.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
D.
hasHighestPeakName
Indicates that the related value is the name of the tallest peak associated with the given entity.
-
E.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 4:49 a.m.