Triple
T2707694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistles of Wisdom |
E59381
|
entity |
| Predicate | consideredByDruze |
P3917
|
FINISHED |
| Object | ultimate religious authority |
—
|
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: ultimate religious authority | Statement: [Epistles of Wisdom, consideredByDruze, ultimate religious authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredByDruze Context triple: [Epistles of Wisdom, consideredByDruze, ultimate religious authority]
-
A.
isConsideredByAdherents
chosen
Indicates that something (such as a belief, practice, object, or figure) is regarded or held in a particular way by the people who adhere to a specific faith, ideology, or group.
-
B.
consideredHeresyBy
Indicates that a belief, practice, or doctrine is judged to be heretical by a particular authority, group, or tradition.
-
C.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
D.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
E.
hasMosque
Indicates that one entity possesses, contains, or is the location of a mosque.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda73de1c81908f5d6b0383e23144 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.