Triple
T34161855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suttungr |
E876298
|
entity |
| Predicate | employsGuardian |
P28704
|
FINISHED |
| Object | Gunnlöð |
—
|
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: Gunnlöð | Statement: [Suttungr, employsGuardian, Gunnlöð]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsGuardian Context triple: [Suttungr, employsGuardian, Gunnlöð]
-
A.
guardian
chosen
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
employsSystem
Indicates that one entity makes use of or operates a particular system to perform its functions or activities.
-
C.
employsOrEmployed
Indicates that one entity currently employs or previously employed another entity in a work or service relationship.
-
D.
employedIncognito
Indicates that one entity is working for or employed by another while deliberately concealing their true identity or role.
-
E.
employedUnder
Indicates that one entity works as an employee under the authority, supervision, or organizational structure of 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:54 a.m.