Triple
T6788860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hud |
E155880
|
entity |
| Predicate | opposedBelief |
P64120
|
FINISHED |
| Object | worship of multiple deities |
—
|
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: worship of multiple deities | Statement: [Hud, opposedBelief, worship of multiple deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedBelief Context triple: [Hud, opposedBelief, worship of multiple deities]
-
A.
opposingIdeology
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
D.
sharesBelief
Indicates that two or more entities hold the same belief or conviction.
-
E.
hasOpposedIdea
chosen
Indicates that one entity holds an idea that conflicts with, contradicts, or stands in opposition to the idea held by another entity.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2aa2e0c8190b994261826ae001d |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.