Triple
T20763652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Ishizuchi area |
E511035
|
entity |
| Predicate | hasMainPeakElevation_m |
P141432
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Mount Ishizuchi area, hasMainPeakElevation_m, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPeakElevation_m Context triple: [Mount Ishizuchi area, hasMainPeakElevation_m, 1982]
-
A.
hasMainMountain
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
B.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
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.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
-
E.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24b18b8819082e61104be6f83a3 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:35 p.m.