Triple
T35616303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR Central (Tokaido Shinkansen) |
E1029176
|
entity |
| Predicate | primaryTerminusWest |
P51120
|
FINISHED |
| Object | Shin-Osaka Station |
E10575
|
NE FINISHED |
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: Shin-Osaka Station | Statement: [JR Central (Tokaido Shinkansen), primaryTerminusWest, Shin-Osaka Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTerminusWest Context triple: [JR Central (Tokaido Shinkansen), primaryTerminusWest, Shin-Osaka Station]
-
A.
hasTerminusWest
chosen
Indicates that something has its western endpoint, terminus, or final stop at the referenced entity.
-
B.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
C.
terminusWestNear
Indicates that the western terminus of one entity is located near the western terminus of another entity.
-
D.
terminusWestBorough
Indicates that something serves as the western terminus or endpoint of a route, line, or connection at a place called Borough.
-
E.
terminusProvinceWest
Indicates that the western terminus of an entity (such as a route or line) is located within a specified province.
- F. None of above.
Provenance (4 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410ca499048190b8a19dc943a34556 |
completed | June 28, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.