Triple
T6196640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Yoshino |
E138523
|
entity |
| Predicate | hasHigherPeaksNearby |
P69599
|
FINISHED |
| Object | Mount Ōmine area |
—
|
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: Mount Ōmine area | Statement: [Mount Yoshino, hasHigherPeaksNearby, Mount Ōmine area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherPeaksNearby Context triple: [Mount Yoshino, hasHigherPeaksNearby, Mount Ōmine area]
-
A.
hasNearbyPeak
Indicates that one location has another peak situated close to it in geographic space.
-
B.
hasNearbyHillRange
Indicates that one entity is located close to or within the vicinity of a range of hills associated with the other entity.
-
C.
hasNearbyPlateau
Indicates that one geographic entity is located close to or adjacent to a plateau.
-
D.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
E.
hasHigherElevationArea
Indicates that one area is situated at a greater elevation above sea level than another 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062508f5c8190a00291708a9a7de9 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:20 p.m.