Triple
T21715893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大船駅 |
E536026
|
entity |
| Predicate | 最寄観光地 |
P21947
|
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.
mostVisitedPartOf
Indicates that one entity is the part or region of another entity that receives the highest number of visits or traffic compared to its other parts.
-
B.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
C.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
D.
prefectureCapitalNearby
Indicates that a prefecture’s capital city is geographically close to the referenced location.
-
E.
journeyDestination
chosen
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
- 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.