Triple
T34995765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 北楼門 |
E1009522
|
entity |
| Predicate | isCulturalHeritageContext |
P33156
|
FINISHED |
| Object | 祇園の歴史的景観の一部 |
—
|
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: 祇園の歴史的景観の一部 | Statement: [北楼門, isCulturalHeritageContext, 祇園の歴史的景観の一部]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCulturalHeritageContext Context triple: [北楼門, isCulturalHeritageContext, 祇園の歴史的景観の一部]
-
A.
hasHeritageContext
chosen
Indicates that something is associated with, influenced by, or situated within a particular cultural, historical, or heritage-related context.
-
B.
isCulturalHeritageSite
Indicates that a place or structure is officially recognized and protected as having significant cultural, historical, or artistic value.
-
C.
isCulturalSignificance
Indicates that something holds notable meaning, value, or influence within a particular culture or cultural context.
-
D.
hasCulturalHeritageOn
Indicates that one entity possesses, preserves, or is associated with the cultural heritage embodied in another entity.
-
E.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.