Triple
T22440373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 吹上御苑 |
E554737
|
entity |
| Predicate | アクセス |
P5872
|
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.
accessTown
Indicates that an entity has the ability or permission to enter or make use of a particular town.
-
B.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
-
C.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
D.
accessible
Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
-
E.
accessDirection
Indicates the direction or orientation from which access to something is obtained or permitted.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae1f82881908a611f134eb03f3d |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.