Triple
T36823693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skjaldarmerki Íslands |
E909949
|
entity |
| Predicate | guardianSpiritRole |
P117155
|
FINISHED |
| Object | protector of the north |
—
|
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: protector of the north | Statement: [Skjaldarmerki Íslands, guardianSpiritRole, protector of the north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianSpiritRole Context triple: [Skjaldarmerki Íslands, guardianSpiritRole, protector of the north]
-
A.
guardianStatuesRole
Indicates the role or function that guardian statues perform in relation to the entities or places they protect.
-
B.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
C.
hasSpiritSymbolRole
chosen
Indicates that an entity serves in a designated role or function specifically associated with a spirit symbol.
-
D.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
E.
guardianShrineOf
Indicates a relationship where one entity serves as a protective or custodial shrine dedicated to another 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.