Triple
T38656705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishima-juku |
E939910
|
entity |
| Predicate | servedRouteBetween |
P24772
|
FINISHED |
| Object | Edo |
—
|
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: Edo | Statement: [Mishima-juku, servedRouteBetween, Edo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedRouteBetween Context triple: [Mishima-juku, servedRouteBetween, Edo]
-
A.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
B.
servesRouteAcross
Indicates that a transportation service operates a route that passes through or spans across a specified area or boundary.
-
C.
servesShippingRoutesBetween
Indicates that something (such as a service, route, or carrier) provides transportation or shipping connections linking two or more locations.
-
D.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
E.
routeBetween
chosen
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
Created at: May 3, 2026, 4:33 p.m.