Triple
T25659443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shia Imams |
E643336
|
entity |
| Predicate | areRegardedAs |
P310
|
FINISHED |
| Object | divinely guided leaders |
—
|
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: divinely guided leaders | Statement: [Shia Imams, areRegardedAs, divinely guided leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areRegardedAs Context triple: [Shia Imams, areRegardedAs, divinely guided leaders]
-
A.
isUnofficiallyRegardedAs
Indicates that something or someone is commonly or informally considered to have a certain role, status, or identity, without any official recognition or formal designation.
-
B.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
C.
membersAreRegardedAs
Indicates that certain individuals or entities are viewed or treated as members of a particular group or organization.
-
D.
areA
Indicates that one entity is classified as a type, instance, or member of another entity or category.
-
E.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
- 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_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 6:50 p.m.