Triple
T25659452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shia Imams |
E643336
|
entity |
| Predicate | areBelievedToBe |
P9182
|
FINISHED |
| Object | appointed by 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: appointed by God | Statement: [Shia Imams, areBelievedToBe, appointed by God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areBelievedToBe Context triple: [Shia Imams, areBelievedToBe, appointed by God]
-
A.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
B.
believedBy
chosen
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
C.
believedProvidedBy
Indicates that something is thought or assumed to have been supplied or made available by a particular source or provider.
-
D.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
E.
believedToBelongTo
Indicates that something is thought or assumed, but not definitively known, to be owned by or part of a particular 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faee68408190b602dc71ec5b83aa |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 6:50 p.m.