Triple
T37221334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin-Osaka – Hakata |
E922889
|
entity |
| Predicate | isWesternSegmentOf |
P31111
|
FINISHED |
| Object | Sanyō Shinkansen corridor |
—
|
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: Sanyō Shinkansen corridor | Statement: [Shin-Osaka – Hakata, isWesternSegmentOf, Sanyō Shinkansen corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWesternSegmentOf Context triple: [Shin-Osaka – Hakata, isWesternSegmentOf, Sanyō Shinkansen corridor]
-
A.
isWesternmostPartOf
Indicates that one entity is the furthest to the west within the geographic extent or boundary of another entity.
-
B.
isAlternateSegmentOf
Indicates that one segment serves as an alternative or substitute to another segment, typically in a sequence, structure, or path.
-
C.
isInWesternPartOf
chosen
Indicates that one entity is located within the western part or region of another entity.
-
D.
separatesWesternEndOf
Indicates that one entity forms a dividing boundary that marks off or distinguishes the western end of another entity.
-
E.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.