Triple
T35319266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karasuma-dori |
E1019990
|
entity |
| Predicate | hasNearbyRailHub |
P31869
|
FINISHED |
| Object | Karasuma Station |
—
|
NE NERFINISHED |
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: Karasuma Station | Statement: [Karasuma-dori, hasNearbyRailHub, Karasuma Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRailHub Context triple: [Karasuma-dori, hasNearbyRailHub, Karasuma Station]
-
A.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
B.
hasNearbyRailwayStation
chosen
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
nearInternationalTransportHub
Indicates that one entity is located close to a major international transportation hub, such as an airport, seaport, or central rail terminal.
-
E.
nearCommuterRailStation
Indicates that one entity is located close to, or within a short walking distance of, a commuter rail station.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:03 p.m.