Triple
T4768627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abrahamic covenant |
E105871
|
entity |
| Predicate | promiseType |
P10241
|
FINISHED |
| Object | promise of land |
—
|
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: promise of land | Statement: [Abrahamic covenant, promiseType, promise of land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promiseType Context triple: [Abrahamic covenant, promiseType, promise of land]
-
A.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
B.
corePromise
chosen
Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
-
C.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
D.
receivedPromiseAbout
Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
-
E.
resolves
Indicates that one entity successfully finds a solution, answer, or outcome for a problem, conflict, or uncertainty involving 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.