Triple
T30600278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of the Mountain |
E778884
|
entity |
| Predicate | regaliaOf |
P80953
|
FINISHED |
| Object | Kings under the Mountain |
—
|
NE NERFINISHED |
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: Kings under the Mountain | Statement: [Heart of the Mountain, regaliaOf, Kings under the Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regaliaOf Context triple: [Heart of the Mountain, regaliaOf, Kings under the Mountain]
-
A.
relatedRegalia
Indicates that there is an association or connection between items of regalia, such as ceremonial garments, insignia, or symbols of office.
-
B.
usesImperialRegalia
Indicates that one entity employs or incorporates imperial regalia (such as crowns, scepters, or other sovereign insignia) in relation to another entity or context.
-
C.
emblemsPartakenBy
Indicates that certain emblems are used, worn, or otherwise participated in by specific entities.
-
D.
ornement
Indicates that one entity serves as an ornament or decorative embellishment for another entity.
-
E.
ceremonialSymbol
chosen
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b0dbe08190aeacfb2d5386b46d |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:25 p.m.