Triple
T26794772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subashiri area of Oyama |
E670914
|
entity |
| Predicate | trailStatus |
P103082
|
FINISHED |
| Object | one of the traditional Mount Fuji ascent routes |
—
|
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: one of the traditional Mount Fuji ascent routes | Statement: [Subashiri area of Oyama, trailStatus, one of the traditional Mount Fuji ascent routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailStatus Context triple: [Subashiri area of Oyama, trailStatus, one of the traditional Mount Fuji ascent routes]
-
A.
hasTrailStatus
chosen
Indicates the current condition or accessibility state assigned to a trail.
-
B.
trailEndpoint
Indicates that one entity marks the terminal point or ending location of a trail defined by another entity.
-
C.
trailNumber
Indicates that an entity is associated with a specific trail identifier or route number within a trail system.
-
D.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
E.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f619bf8738819094583140287f42f0 |
completed | May 2, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:19 a.m.