Triple
T2886576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasaka Shrine |
E59519
|
entity |
| Predicate | cityDistrictRole |
P8652
|
FINISHED |
| Object | guardian shrine of Gion area |
—
|
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: guardian shrine of Gion area | Statement: [Yasaka Shrine, cityDistrictRole, guardian shrine of Gion area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDistrictRole Context triple: [Yasaka Shrine, cityDistrictRole, guardian shrine of Gion area]
-
A.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
B.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
C.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
D.
urbanRole
chosen
Indicates the function, status, or role that an entity holds within an urban or city context.
-
E.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe0463ccc8190bf08330f40d0cfdc |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.