Triple
T8441084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thor |
E199352
|
entity |
| Predicate | motherType |
P83376
|
FINISHED |
| Object | earth goddess |
—
|
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: earth goddess | Statement: [Thor, motherType, earth goddess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherType Context triple: [Thor, motherType, earth goddess]
-
A.
motherIs
Indicates that one entity is the mother (biological or adoptive) of another entity.
-
B.
motherWas
Indicates that one entity was the mother (biological or adoptive) of another entity at some time in the past.
-
C.
motherInstanceOf
Indicates that a specific mother entity is an instance of a more general mother-related class or category.
-
D.
motherFrom
Indicates that one entity is the mother (biological or adoptive) of another entity, specifying a maternal parent-child relationship from the mother to the child.
-
E.
motherStatus
Indicates the current condition, role, or state of an entity in relation to being a mother (e.g., whether and how they are functioning or recognized as a mother).
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:08 p.m.