Triple
T18197621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel II Accord |
E435701
|
entity |
| Predicate | finalTextIssued |
P1695
|
FINISHED |
| Object | June 2004 |
—
|
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: June 2004 | Statement: [Basel II Accord, finalTextIssued, June 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalTextIssued Context triple: [Basel II Accord, finalTextIssued, June 2004]
-
A.
finalIssue
Indicates that an issue or problem is in its last or conclusive state, with no further changes or iterations expected.
-
B.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
C.
issuedDocument
chosen
Indicates that one entity has formally created and provided an official document to another entity.
-
D.
issuedWith
Indicates that one entity is formally provided, granted, or supplied together with another entity as part of the same issuance event.
-
E.
finalRecord
Indicates that a record represents the last or ultimate version/state in a sequence or process.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d47f1c819082eec59492497797 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.