Triple
T23734852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zao Mountains |
E586512
|
entity |
| Predicate | OkamaLocation |
P153461
|
FINISHED |
| Object | between Kumano-dake and Goshiki-dake |
—
|
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: between Kumano-dake and Goshiki-dake | Statement: [Zao Mountains, OkamaLocation, between Kumano-dake and Goshiki-dake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OkamaLocation Context triple: [Zao Mountains, OkamaLocation, between Kumano-dake and Goshiki-dake]
-
A.
eraLocation
Indicates the place or geographic context in which a particular historical era or time period occurs or is primarily associated.
-
B.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
C.
TenjinMatsuriLocation
Indicates the location where the Tenjin Matsuri festival takes place or is held.
-
D.
outfallLocation
Indicates the geographic place where a discharge, such as wastewater or runoff, is released into the environment.
-
E.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bacfb3d0819085a11140ac7aeb12 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:10 p.m.