Triple
T8529202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ismail |
E201898
|
entity |
| Predicate | covenantAssociation |
P83163
|
FINISHED |
| Object | Abrahamic tradition |
—
|
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: Abrahamic tradition | Statement: [Ismail, covenantAssociation, Abrahamic tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenantAssociation Context triple: [Ismail, covenantAssociation, Abrahamic tradition]
-
A.
relatedCovenant
Indicates a relationship in which one covenant is connected to, associated with, or derived from another covenant.
-
B.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
C.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
-
D.
covenantCommunity
Indicates a relationship in which entities are bound together by a shared covenant, forming a committed, mutually obligated community.
-
E.
covenantView
Indicates a relationship where one party observes, understands, or interprets the terms, conditions, or implications of a covenant or binding agreement.
- F. None of above. chosen
Provenance (4 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe67409f08190b20d13d26e9a362c |
completed | March 31, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:17 p.m.