Triple
T31528635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | general obligations |
E804411
|
entity |
| Predicate | mayBeBreachBy |
P180552
|
FINISHED |
| Object | omission |
—
|
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: omission | Statement: [general obligations, mayBeBreachBy, omission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeBreachBy Context triple: [general obligations, mayBeBreachBy, omission]
-
A.
breachedDuring
Indicates that one entity violated, broke, or failed to uphold another entity (such as a rule, contract, or security measure) within a specified time period or event.
-
B.
riskIfBreached
Indicates that a breach of the referenced entity or condition would expose or create a potential risk or harm.
-
C.
breach
Indicates that one party violates, breaks, or fails to uphold an agreed-upon obligation, rule, or boundary in relation to another.
-
D.
mayBeReportedBy
Indicates that an event, condition, or item can potentially be reported or documented by a particular agent or source.
-
E.
hasBreaches
Indicates that one entity experiences, contains, or is affected by one or more security, structural, or policy breaches associated with another entity.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 30, 2026, 10 p.m.