Triple
T8861507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishiyama-dera |
E210897
|
entity |
| Predicate | hasTreasure |
P18543
|
FINISHED |
| Object | Heian-period artworks |
—
|
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: Heian-period artworks | Statement: [Ishiyama-dera, hasTreasure, Heian-period artworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreasure Context triple: [Ishiyama-dera, hasTreasure, Heian-period artworks]
-
A.
hasGoldVault
Indicates that one entity possesses or contains a vault specifically used for storing gold.
-
B.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
C.
containsRelic
chosen
Indicates that one entity holds, includes, or has within it a relic.
-
D.
hasHeirloom
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
E.
tressureType
Indicates the specific kind or category of tressure (a heraldic ornamental border around a shield or charge) associated with an entity.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e860888190a8a8702377db949e |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.