Triple
T31364444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iwashimizu-sai |
E799965
|
entity |
| Predicate | deityRoleHonored |
P118406
|
FINISHED |
| Object | god of war |
—
|
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: god of war | Statement: [Iwashimizu-sai, deityRoleHonored, god of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityRoleHonored Context triple: [Iwashimizu-sai, deityRoleHonored, god of war]
-
A.
honorsDeityAs
Indicates that one entity venerates, worships, or regards another entity as a particular deity or divine figure.
-
B.
roleOfReferencedDeity
chosen
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
C.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
D.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
E.
praisedDeity
Indicates that one entity expressed praise, admiration, or reverence toward a deity.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:18 p.m.