Triple
T27425702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sotetsu Railway |
E690477
|
entity |
| Predicate | majorTerminalStation |
P77374
|
FINISHED |
| Object | Yokohama 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: Yokohama Station | Statement: [Sotetsu Railway, majorTerminalStation, Yokohama Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTerminalStation Context triple: [Sotetsu Railway, majorTerminalStation, Yokohama Station]
-
A.
otherMajorTerminal
Indicates that an entity is associated with a different primary terminal or endpoint than the one currently referenced or considered.
-
B.
formerTerminalStation
Indicates that a location once served as the end point (terminus) of a transportation line or route but no longer holds that status.
-
C.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
D.
middleStation
Indicates that one station lies between two other stations along a route or line, serving as an intermediate point in the sequence.
-
E.
railTerminus
chosen
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 12:40 p.m.