Triple
T27408383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishima Station |
E692072
|
entity |
| Predicate | isOnConventionalRail |
P62786
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Mishima Station, isOnConventionalRail, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnConventionalRail Context triple: [Mishima Station, isOnConventionalRail, true]
-
A.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
B.
isOnRailway
chosen
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
C.
isPassengerRail
Indicates that something functions as or is classified as a passenger rail service or system, primarily used to transport people rather than freight.
-
D.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
E.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd83da48190854bb397bfe4b3ba |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:31 p.m.