Triple
T25417406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karasuma Oike Station |
E636875
|
entity |
| Predicate | hasMultipleExits |
P42028
|
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: [Karasuma Oike Station, hasMultipleExits, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleExits Context triple: [Karasuma Oike Station, hasMultipleExits, true]
-
A.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given entity.
-
B.
hasNumberedExit
Indicates that an entity (such as a road or highway) includes or is associated with an exit that has an assigned number.
-
C.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
D.
hasMultipleEntrances
chosen
Indicates that an entity possesses more than one distinct entrance or access point.
-
E.
hasExits
Indicates that an entity provides one or more ways out or routes leading from it to other locations or states.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 1:55 p.m.