Triple
T32849621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuto Expressway Route 9 Fukagawa Line |
E840209
|
entity |
| Predicate | accessesWard |
P154172
|
FINISHED |
| Object | Kōtō Ward |
—
|
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: Kōtō Ward | Statement: [Shuto Expressway Route 9 Fukagawa Line, accessesWard, Kōtō Ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesWard Context triple: [Shuto Expressway Route 9 Fukagawa Line, accessesWard, Kōtō Ward]
-
A.
containsWard
Indicates that one entity includes, encompasses, or has within it a ward (such as a district, division, or dependent person) as part of its scope or responsibility.
-
B.
isWardOf
Indicates that one entity is under the guardianship, protection, or legal care of another entity as their ward.
-
C.
accessVillage
Indicates that an entity is able to enter, reach, or make use of the facilities or area of a particular village.
-
D.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
-
E.
accessArea
chosen
Indicates that an entity is permitted to enter, use, or interact with a specified physical or logical area.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:17 a.m.