Triple
T31959171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menrva |
E815986
|
entity |
| Predicate | typeOfWarDeity |
P85058
|
FINISHED |
| Object | strategic war deity |
—
|
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: strategic war deity | Statement: [Menrva, typeOfWarDeity, strategic war deity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWarDeity Context triple: [Menrva, typeOfWarDeity, strategic war deity]
-
A.
hasWarDeity
Indicates that an entity has a specific deity associated with war as part of its religious or mythological system.
-
B.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
C.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
D.
deityCategory
chosen
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
E.
associatedDeityOrForce
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
Created at: May 1, 2026, 12:08 a.m.