Triple
T33170708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimoda |
E849021
|
entity |
| Predicate | connectedByRailLine |
P177940
|
FINISHED |
| Object | Izu Kyūkō 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: Izu Kyūkō Line | Statement: [Shimoda, connectedByRailLine, Izu Kyūkō Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByRailLine Context triple: [Shimoda, connectedByRailLine, Izu Kyūkō Line]
-
A.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
B.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
C.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
-
D.
railroadLineServed
chosen
Indicates that a particular railroad line provides service to, or operates through, a given location or facility.
-
E.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 1, 2026, 1:28 a.m.