Triple
T31016543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大熊町 |
E790338
|
entity |
| Predicate | transportAccessBefore2011 |
P192563
|
FINISHED |
| Object | 常磐線沿線地域 |
—
|
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: 常磐線沿線地域 | Statement: [大熊町, transportAccessBefore2011, 常磐線沿線地域]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportAccessBefore2011 Context triple: [大熊町, transportAccessBefore2011, 常磐線沿線地域]
-
A.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
B.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
C.
hasHistoricTransportLink
chosen
Indicates that there is or was a historically significant transportation connection between the related entities.
-
D.
transportAccessFrom
Indicates that one location or entity has transportation access originating from another specified location or source.
-
E.
transportAccessType
Indicates the type or mode of transportation access available or used in a given context.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 8:57 p.m.