Triple
T20666556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamashina-dera |
E507902
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Yamashina |
—
|
NE NERFINISHED |
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: Yamashina | Statement: [Yamashina-dera, locatedIn, Yamashina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yamashina Context triple: [Yamashina-dera, locatedIn, Yamashina]
-
A.
Yamashina
chosen
Yamashina is a Japanese noble family name historically associated with a cadet branch of the Imperial Family.
-
B.
Yagiyama
Yagiyama is a hilly district in Sendai, Japan, known for its zoo, amusement park, and scenic views over the city.
-
C.
Ōyama
Ōyama is a Japanese surname borne by various notable figures in Japan’s military, political, and cultural history.
-
D.
Maihara
Maihara was a former town in Shiga Prefecture, Japan, that later became part of the city of Maibara through a municipal merger.
-
E.
Oyama
Oyama is a city in Tochigi Prefecture, Japan, known as a key commercial and transportation hub within the northern Kantō region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c39dd48190965d65537592aef6 |
completed | April 20, 2026, 11:24 p.m. |
Created at: April 16, 2026, 11:44 a.m.