Triple
T20643783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dar al-Ahd (in some juristic usages) |
E507297
|
entity |
| Predicate | mayBeTerminatedBy |
P87518
|
FINISHED |
| Object | material breach of the 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: material breach of the covenant | Statement: [Dar al-Ahd (in some juristic usages), mayBeTerminatedBy, material breach of the covenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeTerminatedBy Context triple: [Dar al-Ahd (in some juristic usages), mayBeTerminatedBy, material breach of the covenant]
-
A.
canTerminate
Indicates that one entity has the authority or ability to end or discontinue another entity, process, or relationship.
-
B.
terminatesFor
Indicates that one entity causes or marks the ending or cessation of another entity, process, or state.
-
C.
typicallyTerminatedIn
Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
-
D.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
E.
natureOfTermination
chosen
Indicates the manner, cause, or conditions under which a relationship, contract, or employment is brought to an end.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af1d0be481909e090193dcfd9cf6 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.