Triple
T2567380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR Kobe Line |
E57383
|
entity |
| Predicate | commuterFunction |
P3916
|
FINISHED |
| Object | links central Osaka with Kobe city center |
—
|
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: links central Osaka with Kobe city center | Statement: [JR Kobe Line, commuterFunction, links central Osaka with Kobe city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commuterFunction Context triple: [JR Kobe Line, commuterFunction, links central Osaka with Kobe city center]
-
A.
commuterServiceTo
Indicates a transportation service that regularly carries commuters to a specified destination.
-
B.
commutesBetween
Indicates a regular pattern of travel back and forth between two locations, typically for work, study, or routine activities.
-
C.
hasCommuterTraffic
Indicates that there is regular, recurring traffic flow associated with people traveling between their homes and places of work or study.
-
D.
hasCommuterOrientation
chosen
Indicates that an entity is designed or intended primarily for use by commuters, emphasizing suitability for regular travel between home and work or study.
-
E.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3602ed08190aad0f9c7ac577eb0 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.