Triple
T6066291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumsusan Palace of the Sun |
E135168
|
entity |
| Predicate | convertedToMausoleum |
P68452
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Kumsusan Palace of the Sun, convertedToMausoleum, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToMausoleum Context triple: [Kumsusan Palace of the Sun, convertedToMausoleum, 1994]
-
A.
convertedToPermanentCemetery
Indicates that a site or burial ground previously used in a temporary or different capacity has been formally designated and established as a permanent cemetery.
-
B.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
C.
hasPartInMausoleum
Indicates that an entity is a component, section, or element contained within or forming part of a mausoleum.
-
D.
turnedToStone
Indicates that an entity has been transformed into stone, typically as a result of some magical or supernatural effect.
-
E.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
- F. None of above. chosen
Provenance (4 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0573f17088190a728f1c290cc9d1d |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:10 p.m.