Triple
T22440412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伏見櫓 |
E554738
|
entity |
| Predicate | 歴史的価値 |
P35816
|
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: [伏見櫓, 歴史的価値, 江戸城における貴重な現存櫓]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 歴史的価値 Context triple: [伏見櫓, 歴史的価値, 江戸城における貴重な現存櫓]
-
A.
heritageValue
Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
-
B.
historicalValue
chosen
Indicates that something possesses significance, importance, or relevance due to its connection with past events, periods, or developments.
-
C.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
D.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
E.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae1f82881908a611f134eb03f3d |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.