Triple
T158210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tritheism |
E3223
|
entity |
| Predicate | evaluatedAs |
P4529
|
FINISHED |
| Object | incompatible with biblical monotheism |
—
|
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: incompatible with biblical monotheism | Statement: [Tritheism, evaluatedAs, incompatible with biblical monotheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatedAs Context triple: [Tritheism, evaluatedAs, incompatible with biblical monotheism]
-
A.
assessedBy
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
-
B.
interpretedAs
chosen
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
-
C.
constructedAs
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
-
D.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
E.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.