Triple
T27947019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqidah |
E700908
|
entity |
| Predicate | requiresAffirmationOf |
P85756
|
FINISHED |
| Object | oneness of God |
—
|
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: oneness of God | Statement: [Aqidah, requiresAffirmationOf, oneness of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAffirmationOf Context triple: [Aqidah, requiresAffirmationOf, oneness of God]
-
A.
requiresAdviceAndApprovalOf
Indicates that one entity can proceed with an action or decision only if it first seeks guidance and obtains formal approval from another entity.
-
B.
confirmationRequirement
chosen
Indicates that an action, decision, or change is contingent on receiving explicit confirmation from a specified party or process.
-
C.
requiresProofIn
Indicates that one entity must be justified, validated, or supported by formal proof within the context or framework specified by another entity.
-
D.
requiresProofOf
Indicates that one entity must provide formal evidence or documentation to validate or authorize another entity.
-
E.
requiresAgreementWith
Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 27, 2026, 7:22 p.m.