Triple
T18136695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel I Accord |
E434154
|
entity |
| Predicate | capitalAdequacyRatio |
P31816
|
FINISHED |
| Object | 8 percent |
—
|
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: 8 percent | Statement: [Basel I Accord, capitalAdequacyRatio, 8 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalAdequacyRatio Context triple: [Basel I Accord, capitalAdequacyRatio, 8 percent]
-
A.
authorizedCapital
Indicates the legally approved maximum amount of share capital that a company is permitted to issue under its corporate charter or governing documents.
-
B.
capitalStructure
Indicates the financial relationship defining how an entity is funded through a mix of debt, equity, and other securities.
-
C.
hasCreditRatingAgencyCoverage
Indicates that an entity is monitored, evaluated, or rated by a credit rating agency.
-
D.
requiresMinimumCapital
chosen
Indicates that one entity can only proceed, be valid, or be permitted if a specified minimum amount of capital is available or provided.
-
E.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
- 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.