Triple
T27650031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-14 |
E696824
|
entity |
| Predicate | correspondsToStation |
P41163
|
FINISHED |
| Object | Kitasando Station |
—
|
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: Kitasando Station | Statement: [F-14, correspondsToStation, Kitasando Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToStation Context triple: [F-14, correspondsToStation, Kitasando Station]
-
A.
associatedWithStationName
chosen
Indicates a relationship where something is linked or connected to a particular station identified by its name.
-
B.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
C.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
-
D.
connectsAtStation
Indicates that one transportation service or route links to another at a specific station, allowing passengers to transfer between them there.
-
E.
identifiesStationWithinLine
Indicates that a specific station is recognized as belonging to, or located within, a particular transit line.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 2:31 p.m.