Triple
T648757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moses |
E11297
|
entity |
| Predicate | covenantRole |
P11687
|
FINISHED |
| Object | mediator of the Sinai covenant |
—
|
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: mediator of the Sinai covenant | Statement: [Moses, covenantRole, mediator of the Sinai covenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenantRole Context triple: [Moses, covenantRole, mediator of the Sinai covenant]
-
A.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
B.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
-
C.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between parties.
-
D.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
E.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f308f34819094ba28cfc786051e |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0c0dcc8190849211d45489a5a7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.