Triple
T2707688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistles of Wisdom |
E59381
|
entity |
| Predicate | doctrineContains |
P15801
|
FINISHED |
| Object | tawhid |
—
|
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: tawhid | Statement: [Epistles of Wisdom, doctrineContains, tawhid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineContains Context triple: [Epistles of Wisdom, doctrineContains, tawhid]
-
A.
containsDoctrine
chosen
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
-
B.
hasCollectionItemBy
Indicates that an entity possesses or includes a specific item as part of its collection, identified or referenced by some key or identifier.
-
C.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
D.
isCollectionOf
Indicates that one entity is a group or aggregate composed of multiple instances or elements of another entity.
-
E.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda73de1c81908f5d6b0383e23144 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.