Triple
T10044644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghafir |
E207583
|
entity |
| Predicate | containsPromiseTo |
P10010
|
FINISHED |
| Object | Believers |
—
|
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: Believers | Statement: [Ghafir, containsPromiseTo, Believers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPromiseTo Context triple: [Ghafir, containsPromiseTo, Believers]
-
A.
hasPromiseType
Indicates that an entity is associated with, or classified by, a specific type or category of promise.
-
B.
corePromise
Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
-
C.
promises
chosen
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
D.
childOfPromiseThrough
Indicates a relationship where an entity is considered a child or descendant specifically by virtue of a promise or covenant, rather than by ordinary lineage or means.
-
E.
promiseScope
Indicates that one entity has made a commitment or assurance to another entity regarding a specific action, condition, or outcome within a defined scope or context.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf61b3e08190b69bcf67b6a95342 |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.