Triple
T19267825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wakakusa-yama |
E481834
|
entity |
| Predicate | hasClimbingTrail |
P135365
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wakakusa-yama, hasClimbingTrail, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingTrail Context triple: [Wakakusa-yama, hasClimbingTrail, yes]
-
A.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
B.
hasClimbingActivity
Indicates that an entity engages in or is associated with a climbing-related activity.
-
C.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
D.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
E.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8e1f888190a95f60fa29ca3b98 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.