Triple
T28626965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingu |
E724550
|
entity |
| Predicate | sideInDivineConflict |
P6060
|
FINISHED |
| Object | Tiamat’s forces |
—
|
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: Tiamat’s forces | Statement: [Kingu, sideInDivineConflict, Tiamat’s forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInDivineConflict Context triple: [Kingu, sideInDivineConflict, Tiamat’s forces]
-
A.
roleInTheWrathOfGod
Indicates that an entity has a specific role or participation in the event, concept, or narrative referred to as "the Wrath of God."
-
B.
opposesDeity
Indicates a relationship where an entity is in conflict with, resists, or acts against a deity.
-
C.
opponentInSchism
Indicates that two parties stand on opposing sides within the same internal division, dispute, or schismatic conflict.
-
D.
conflictRole
chosen
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
E.
engagesInCyclicalStruggleWith
Indicates a relationship in which two entities are locked in a recurring, back-and-forth conflict or opposition that repeats over time.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:36 a.m.