Triple
T8199999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China Town (Kagoshima) |
E191544
|
entity |
| Predicate | roadAccessWithin |
P73526
|
FINISHED |
| Object | Kagoshima Prefecture road network |
—
|
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: Kagoshima Prefecture road network | Statement: [China Town (Kagoshima), roadAccessWithin, Kagoshima Prefecture road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessWithin Context triple: [China Town (Kagoshima), roadAccessWithin, Kagoshima Prefecture road network]
-
A.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
B.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
C.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
D.
roadCorridorIncludes
chosen
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
E.
hasNoDirectRoadAccess
Indicates that there is no direct road connection available between the relevant locations or entities.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df565dc819099537fc06b694b40 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.