Triple
T7071126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metro Hibiya Line at Kayabacho |
E164697
|
entity |
| Predicate | isKeyAccessPoint |
P26211
|
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 Hibiya Line at Kayabacho, isKeyAccessPoint, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyAccessPoint Context triple: [Tokyo Metro Hibiya Line at Kayabacho, isKeyAccessPoint, true]
-
A.
isMajorAccessPointFor
chosen
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
-
B.
hasKeyPoint
Indicates that one entity includes, contains, or is associated with a specific key point or main idea represented by another entity.
-
C.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
D.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
E.
isKeyEndpointOf
Indicates that one endpoint in a connection, link, or structure serves as the primary or designated key endpoint of the other.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4c862f481908d1faf6ed57774f1 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.