Triple
T1092247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metis |
E24190
|
entity |
| Predicate | grandchildThroughAthena |
P23385
|
FINISHED |
| Object | none traditionally mentioned |
—
|
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: none traditionally mentioned | Statement: [Metis, grandchildThroughAthena, none traditionally mentioned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandchildThroughAthena Context triple: [Metis, grandchildThroughAthena, none traditionally mentioned]
-
A.
grandchild
Indicates that one entity is the child of another entity’s child, i.e., a descendant two generations down.
-
B.
grandchildren
Indicates a familial relationship where one entity is the child of another entity’s child.
-
C.
grandparent
Indicates that one entity is the parent of another entity’s parent.
-
D.
auntOf
Indicates that one person is the aunt of another, typically as the sibling (or sibling-in-law) of a parent or sometimes an older female relative in an extended family role.
-
E.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b982018481908b222df095e318c0 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:42 p.m.