Triple
T19268071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanigawadake Ropeway |
E481841
|
entity |
| Predicate | lowerStationName |
P57205
|
FINISHED |
| Object | Doai Station 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: Doai Station area | Statement: [Tanigawadake Ropeway, lowerStationName, Doai Station area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerStationName Context triple: [Tanigawadake Ropeway, lowerStationName, Doai Station area]
-
A.
hasLowerStation
Indicates that one entity occupies a lower rank, status, or position in a hierarchy relative to another entity.
-
B.
hasLowerStationAt
Indicates that one entity has a subordinate or lower-ranked position relative to another entity within a hierarchical structure.
-
C.
lowerLocation
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
-
D.
lowerTierName
Indicates that one entity is identified as the name or label of a lower or subordinate tier within a hierarchical structure relative to another entity.
-
E.
lowerTerminus
chosen
Indicates that one entity serves as the lower endpoint or downstream terminus of another entity, such as a route, segment, or connection.
- 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_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. |
Created at: April 10, 2026, 1:29 p.m.