Triple
T6547158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metro Chiyoda Line Omotesando Station |
E151037
|
entity |
| Predicate | hasUndergroundPassages |
P58560
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tokyo Metro Chiyoda Line Omotesando Station, hasUndergroundPassages, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundPassages Context triple: [Tokyo Metro Chiyoda Line Omotesando Station, hasUndergroundPassages, true]
-
A.
hasUnderpass
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
-
B.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
C.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
D.
hasUndergroundFacilities
chosen
Indicates that one entity possesses or contains facilities or infrastructure located below ground level in relation to another entity.
-
E.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:50 p.m.