Triple
T9990156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mot |
E196864
|
entity |
| Predicate | sharesMythicTypeWith |
P48089
|
FINISHED |
| Object | other Near Eastern death gods |
—
|
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: other Near Eastern death gods | Statement: [Mot, sharesMythicTypeWith, other Near Eastern death gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMythicTypeWith Context triple: [Mot, sharesMythicTypeWith, other Near Eastern death gods]
-
A.
sharesTypeWith
chosen
Indicates that two entities belong to the same type or category.
-
B.
sharesCharacterWith
Indicates that two entities have at least one character (such as a letter, symbol, or glyph) in common.
-
C.
sharesRoleWith
Indicates that two entities hold the same role or position within a given context or system.
-
D.
sharesRuleWith
Indicates that two or more entities are governed by, comply with, or are associated with the same rule or set of rules.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc7a0cb6481908d7bd1b43f93bd18 |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.