Triple
T35788772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gleanings from the Writings of Bahá'u'lláh |
E1034631
|
entity |
| Predicate | containsTextBy |
P81389
|
FINISHED |
| Object | Bahá'u'lláh |
—
|
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: Bahá'u'lláh | Statement: [Gleanings from the Writings of Bahá'u'lláh, containsTextBy, Bahá'u'lláh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTextBy Context triple: [Gleanings from the Writings of Bahá'u'lláh, containsTextBy, Bahá'u'lláh]
-
A.
containsText
Indicates that one entity includes the specified text string within its content.
-
B.
hasTextBy
chosen
Indicates that one entity (such as a document, work, or record) contains or is associated with text authored or written by another entity.
-
C.
hasTextIn
Indicates that an entity contains or is associated with a specific piece of text within a particular context or location.
-
D.
containsTextsFor
Indicates that one entity holds or includes text content intended for use by another entity.
-
E.
usesTextBy
Indicates that one entity makes use of or relies on a text authored or provided 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.