Triple
T28813362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 奥穂高岳 |
E727574
|
entity |
| Predicate | 隣接する主な山 |
P24277
|
FINISHED |
| Object | 前穂高岳 |
—
|
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: 前穂高岳 | Statement: [奥穂高岳, 隣接する主な山, 前穂高岳]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 隣接する主な山 Context triple: [奥穂高岳, 隣接する主な山, 前穂高岳]
-
A.
adjacentMountain
chosen
Indicates that one mountain is directly next to or touching another mountain, with no significant separation between them.
-
B.
hasMainMountain
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
C.
adjacentLandform
Indicates that two landforms are directly next to each other in space, sharing a common boundary or lying in immediate proximity.
-
D.
neighboringMassif
Indicates that one massif is geographically adjacent to or directly bordering another massif.
-
E.
otherMajorPeak
Indicates that one peak is another significant or prominent peak associated with, but distinct from, a given primary peak.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.