Triple
T9296281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōkuma, Fukushima Prefecture |
E223645
|
entity |
| Predicate | hasRailAccessBefore2011 |
P57688
|
FINISHED |
| Object | Jōban Line |
—
|
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: Jōban Line | Statement: [Ōkuma, Fukushima Prefecture, hasRailAccessBefore2011, Jōban Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailAccessBefore2011 Context triple: [Ōkuma, Fukushima Prefecture, hasRailAccessBefore2011, Jōban Line]
-
A.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
B.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
-
C.
railwayAccess
chosen
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
-
D.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
-
E.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089c9c588190967404c9eb938dfb |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.