Triple
T25389624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yokohama Minatomirai Railway Minatomirai Line |
E636124
|
entity |
| Predicate | locatedUndergroundIn |
P42731
|
FINISHED |
| Object | central Yokohama |
—
|
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: central Yokohama | Statement: [Yokohama Minatomirai Railway Minatomirai Line, locatedUndergroundIn, central Yokohama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedUndergroundIn Context triple: [Yokohama Minatomirai Railway Minatomirai Line, locatedUndergroundIn, central Yokohama]
-
A.
placedUndergroundDuring
Indicates that an entity was located or positioned beneath the ground for the duration of a specified time or event.
-
B.
subterranean
chosen
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
C.
undergroundZone
Indicates that something is located in, associated with, or occurring within an area beneath the ground surface.
-
D.
integratedIntoUnderground
Indicates that something has been incorporated or absorbed into an underground system, structure, or environment.
-
E.
hasUndergroundOrgan
Indicates that an entity possesses an organ or structure that is located below the ground surface.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 21, 2026, 1:49 p.m.