Triple
T11081417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gotemba Trail |
E262002
|
entity |
| Predicate | distanceToSummit |
P97110
|
FINISHED |
| Object | longest among main Mount Fuji trails |
—
|
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: longest among main Mount Fuji trails | Statement: [Gotemba Trail, distanceToSummit, longest among main Mount Fuji trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSummit Context triple: [Gotemba Trail, distanceToSummit, longest among main Mount Fuji trails]
-
A.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
B.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
C.
stoppedDistanceBelowSummit
Indicates that an entity came to a stop at a location that is a certain distance short of reaching the summit.
-
D.
positionRelativeToSummit
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
E.
numberOfStepsToSummit
Indicates the total count of steps required to reach the summit from a specified starting point.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799985650819089b2c0f35a212414 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.