Triple
T18136702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel I Accord |
E434154
|
entity |
| Predicate | doesNotExplicitlyCover |
P10124
|
FINISHED |
| Object | market risk in original framework |
—
|
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: market risk in original framework | Statement: [Basel I Accord, doesNotExplicitlyCover, market risk in original framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotExplicitlyCover Context triple: [Basel I Accord, doesNotExplicitlyCover, market risk in original framework]
-
A.
doesNotCover
chosen
Indicates that one entity fails to include, protect, or extend over another entity or area.
-
B.
doesNotSpecify
Indicates that the subject intentionally leaves some information, detail, or attribute undefined or unspecified with respect to the object.
-
C.
doesNotFullyExplain
Indicates that one entity’s explanation of another entity, event, or situation is incomplete or insufficient to account for it fully.
-
D.
doesNotDefine
Indicates that one entity does not provide a definition, specification, or determining description for another entity.
-
E.
doesNotImply
Indicates that the truth of one statement or condition does not guarantee or lead to the truth of another statement or condition.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de07b4b4819085fe80beb7addfd0 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.