Triple
T33612906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yari-Hotaka traverse |
E861035
|
entity |
| Predicate | hasApproachPoint |
P30202
|
FINISHED |
| Object | Kamikochi |
—
|
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: Kamikochi | Statement: [Yari-Hotaka traverse, hasApproachPoint, Kamikochi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachPoint Context triple: [Yari-Hotaka traverse, hasApproachPoint, Kamikochi]
-
A.
hasApproachTrail
Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
-
B.
hasApproachFeature
Indicates that something possesses a characteristic, element, or quality specifically related to its method, strategy, or manner of approach.
-
C.
hasApproachTime
Indicates that an entity is associated with a specific time at which it approaches or comes near another entity or location.
-
D.
hasApproachSide
chosen
Indicates that one entity has a particular side or direction from which another entity can approach or access it.
-
E.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 1:41 a.m.