Triple
T26122148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyoto Shiyakusho-mae Station |
E658998
|
entity |
| Predicate | nearbyPublicBuilding |
P61270
|
FINISHED |
| Object | Kyoto City Hall |
—
|
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: Kyoto City Hall | Statement: [Kyoto Shiyakusho-mae Station, nearbyPublicBuilding, Kyoto City Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPublicBuilding Context triple: [Kyoto Shiyakusho-mae Station, nearbyPublicBuilding, Kyoto City Hall]
-
A.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
-
B.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
D.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
E.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 26, 2026, 8:09 p.m.