Triple
T21715884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大船駅 |
E536026
|
entity |
| Predicate | 地域拠点性 |
P117896
|
FINISHED |
| Object | 湘南エリア有数のターミナル駅 |
—
|
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: 湘南エリア有数のターミナル駅 | Statement: [大船駅, 地域拠点性, 湘南エリア有数のターミナル駅]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 地域拠点性 Context triple: [大船駅, 地域拠点性, 湘南エリア有数のターミナル駅]
-
A.
featuresRegionalProximity
Indicates that one entity is located near or in close geographic proximity to a particular region or another entity.
-
B.
regionalCharacteristic
Indicates that a particular feature, quality, or attribute is typical of, or distinctive to, a specific geographic region.
-
C.
servesAsRegionalCenterFor
chosen
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
-
D.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
E.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96ab4c88190b76f4a6b7c855039 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.