Triple
T34070674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dies |
E873758
|
entity |
| Predicate | oppositeDeity |
P135855
|
FINISHED |
| Object | Nox |
—
|
NE NERFINISHED |
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: Nox | Statement: [Dies, oppositeDeity, Nox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeDeity Context triple: [Dies, oppositeDeity, Nox]
-
A.
opposesDeity
chosen
Indicates a relationship where an entity is in conflict with, resists, or acts against a deity.
-
B.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
C.
comparableDeity
Indicates that one deity is considered comparable to another in terms of role, attributes, status, or function.
-
D.
associatedDeityOrForce
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
E.
orientationOfDeity
Indicates the directional or positional alignment associated with a deity in relation to a reference point or context.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.