Triple
T14237415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chūgoku Mountains |
E352919
|
entity |
| Predicate | extendsThroughPrefecture |
P99780
|
FINISHED |
| Object | Tottori Prefecture |
—
|
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: Tottori Prefecture | Statement: [Chūgoku Mountains, extendsThroughPrefecture, Tottori Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsThroughPrefecture Context triple: [Chūgoku Mountains, extendsThroughPrefecture, Tottori Prefecture]
-
A.
passesPrefecture
chosen
Indicates that a route, path, or entity traverses through or goes across a specified prefecture.
-
B.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
-
C.
flowsThroughPrefecture
Indicates that something, typically a river or waterway, passes through or traverses the geographic area of a specified prefecture.
-
D.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
-
E.
hostPrefecture
Indicates the prefecture that serves as the host location for an event, activity, or entity.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.