Triple
T31306767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bábís |
E798352
|
entity |
| Predicate | doctrineIncluded |
P17738
|
FINISHED |
| Object | abrogation of certain Islamic laws |
—
|
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: abrogation of certain Islamic laws | Statement: [Bábís, doctrineIncluded, abrogation of certain Islamic laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineIncluded Context triple: [Bábís, doctrineIncluded, abrogation of certain Islamic laws]
-
A.
doctrineRefined
Indicates that an existing doctrine has been further developed, clarified, or improved in its formulation or application.
-
B.
doctrineExplainedBy
Indicates that an explanation or interpretation is provided for a particular doctrine by a specified source or agent.
-
C.
doctrineBasisFor
Indicates that one doctrine serves as a foundational justification, support, or underlying basis for another doctrine or position.
-
D.
doctrineFocus
chosen
Indicates that a doctrine, teaching, or belief is primarily concerned with, centered on, or directed toward a particular subject or theme.
-
E.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.