Triple
T37749785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR Kyushu Hotels |
E940947
|
entity |
| Predicate | usesRailwayNetworkOf |
P15040
|
FINISHED |
| Object | Kyushu Railway Company |
—
|
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: Kyushu Railway Company | Statement: [JR Kyushu Hotels, usesRailwayNetworkOf, Kyushu Railway Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRailwayNetworkOf Context triple: [JR Kyushu Hotels, usesRailwayNetworkOf, Kyushu Railway Company]
-
A.
appliesToRailwayNetwork
Indicates that something is relevant or specifically applicable to a railway network as a whole.
-
B.
usesRailInfrastructureOf
chosen
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
C.
belongsToRailNetwork
Indicates that something is part of, or included within, a specific rail network.
-
D.
connectsToRailwayNetwork
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
-
E.
operatesRailNetworkOf
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.