Triple
T20160360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukuhashi, Fukuoka |
E491686
|
entity |
| Predicate | hasRailLinks |
P13914
|
FINISHED |
| Object | convenient |
—
|
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: convenient | Statement: [Yukuhashi, Fukuoka, hasRailLinks, convenient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailLinks Context triple: [Yukuhashi, Fukuoka, hasRailLinks, convenient]
-
A.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
B.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
C.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
D.
hasMajorRailLinksTo
chosen
Indicates that there are significant railway connections or routes between two locations.
-
E.
hasRailInterchangeFunction
Indicates that something serves as a location or facility where rail lines connect or intersect, allowing passengers or goods to transfer between them.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e37c8c8190827839291027d9e2 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.