Triple
T15679055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ithna Ashariyya |
E377522
|
entity |
| Predicate | sharesBeliefWith |
P11415
|
FINISHED |
| Object | other Shia branches |
—
|
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: other Shia branches | Statement: [Ithna Ashariyya, sharesBeliefWith, other Shia branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBeliefWith Context triple: [Ithna Ashariyya, sharesBeliefWith, other Shia branches]
-
A.
sharesBelief
chosen
Indicates that two or more entities hold the same belief or conviction.
-
B.
beliefCommunicatedThrough
Indicates that a belief held by one entity is conveyed or expressed to another entity through a particular medium, channel, or communicative act.
-
C.
relatedBelief
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
D.
linkedToBelief
Indicates that one entity is connected or associated with a particular belief, such that the belief influences, characterizes, or is attributed to that entity.
-
E.
revealsBeliefsOf
Indicates that one entity makes known, exposes, or discloses the beliefs held by another 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2f1640819086efd5a73bb9734a |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.