Triple
T34274750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Odin |
E879419
|
entity |
| Predicate | hasMembersWithDifferentMothers |
P198887
|
FINISHED |
| Object | Frigg |
—
|
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: Frigg | Statement: [Children of Odin, hasMembersWithDifferentMothers, Frigg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMembersWithDifferentMothers Context triple: [Children of Odin, hasMembersWithDifferentMothers, Frigg]
-
A.
hasTwoMothers
Indicates that an entity is related to or cared for by two distinct mother figures.
-
B.
possibleMother
Indicates that one entity could be the biological or adoptive mother of another, but this relationship is uncertain or not definitively established.
-
C.
hasUncertainParentage
Indicates that the parent or parents of an entity are unknown, disputed, or not reliably established.
-
D.
notMotherOf
Indicates that the subject is explicitly not the mother (biological, adoptive, or recognized maternal parent) of the object.
-
E.
possibleMotherOnly
Indicates that an entity is inferred or hypothesized to be the mother of another entity, but this relationship is not confirmed and remains only a possible maternal link.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: May 1, 2026, 1:56 a.m.