Triple
T30751855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitáb-i-‘Ahd |
E782975
|
entity |
| Predicate | affirmsRoleOf |
P29074
|
FINISHED |
| Object | ‘Abdu’l‑Bahá |
—
|
NE NERFINISHED |
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: ‘Abdu’l‑Bahá | Statement: [Kitáb-i-‘Ahd, affirmsRoleOf, ‘Abdu’l‑Bahá]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affirmsRoleOf Context triple: [Kitáb-i-‘Ahd, affirmsRoleOf, ‘Abdu’l‑Bahá]
-
A.
acknowledgesRoleOf
Indicates that one entity explicitly recognizes and accepts the position, function, or authority that another entity holds.
-
B.
authorityAffirmedBy
Indicates that the legitimacy or validity of an authority is confirmed, endorsed, or supported by another party or source.
-
C.
reaffirmsAuthorityOf
chosen
Indicates that one entity confirms, strengthens, or restates the legitimacy or power of another entity’s authority.
-
D.
affirms
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
E.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f91f0cc8190936582859f7d1683 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.