Triple
T30746980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardian of the Cause of God |
E782839
|
entity |
| Predicate | firstGuardian |
P204117
|
FINISHED |
| Object | Shoghi Effendi |
E318659
|
NE 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: Shoghi Effendi | Statement: [Guardian of the Cause of God, firstGuardian, Shoghi Effendi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGuardian Context triple: [Guardian of the Cause of God, firstGuardian, Shoghi Effendi]
-
A.
motherRole
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
B.
parent
Indicates a relationship where one entity is the direct mother or father of another entity, from whom that other entity is descended.
-
C.
stepfatherOf
Indicates that one person is the male spouse or partner of a child's parent, but is not the child's biological or adoptive father.
-
D.
motherFather
Indicates that the two entities are the biological parents (mother and father) of a child or offspring.
-
E.
caregiverOf
Indicates a relationship where one entity provides ongoing care, support, or supervision for another entity’s well-being.
- F. None of above. chosen
Provenance (5 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0326d40cb88190802f61fa832f8ca8 |
completed | May 12, 2026, 1:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e0b73d88190a6e80588bb4ba543 |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_6a03268b4f9c8190b3e135b37ed373c3 |
completed | May 12, 2026, 1:09 p.m. |
| PDg | Predicate description generation | batch_6a0326d30068819096da11fba14c2f31 |
completed | May 12, 2026, 1:10 p.m. |
Created at: April 29, 2026, 8:38 p.m.