Triple
T6517326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qos |
E148297
|
entity |
| Predicate | comparativeReligion |
P71340
|
FINISHED |
| Object | sometimes compared to Yahweh |
—
|
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: sometimes compared to Yahweh | Statement: [Qos, comparativeReligion, sometimes compared to Yahweh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparativeReligion Context triple: [Qos, comparativeReligion, sometimes compared to Yahweh]
-
A.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
B.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
C.
otherMajorReligion
Indicates that an entity’s primary religious affiliation is a major religion other than the one currently in focus or being referenced.
-
D.
religiousTextTradition
Indicates that a religious text is associated with, originates from, or is authoritative within a particular religious tradition or denomination.
-
E.
religionCommon
Indicates that the related entities share the same religion or religious affiliation.
- F. None of above. chosen
Provenance (4 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0ece2081909c14accef90efd7c |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:44 p.m.