Triple
T16028005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 北の丸公園 |
E388767
|
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.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
B.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
-
C.
accessFeature
Indicates that one entity is permitted to use or interact with a specific feature or capability of another entity.
-
D.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
E.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.