Triple
T2346981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deposit Insurance Fund |
E45152
|
entity |
| Predicate | effectiveDateOfFormation |
P9196
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Deposit Insurance Fund, effectiveDateOfFormation, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveDateOfFormation Context triple: [Deposit Insurance Fund, effectiveDateOfFormation, 2006]
-
A.
establishedAt
chosen
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
B.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
-
C.
formalizationDate
Indicates the date on which something is officially established, formalized, or brought into an official or legally recognized form.
-
D.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
E.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.