Triple
T29992160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DZ Bank |
E761909
|
entity |
| Predicate | foundedAsCurrentFormIn |
P763
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [DZ Bank, foundedAsCurrentFormIn, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCurrentFormIn Context triple: [DZ Bank, foundedAsCurrentFormIn, 2001]
-
A.
establishedInCurrentFormBy
Indicates that one entity created, organized, or defined another entity in the specific structure or configuration in which it currently exists.
-
B.
establishedInCurrentForm
chosen
Indicates the point in time when something took on its present structure, organization, or configuration, distinct from any earlier versions or forms.
-
C.
extantForm
Indicates that a given entity currently exists in a particular form or manifestation.
-
D.
combinedAsCurrentForm
Indicates that multiple prior entities have been merged or integrated to constitute the current form of the subject entity.
-
E.
foundedAsCurrentConfiguration
Indicates that an entity was originally established in the same organizational or structural form in which it currently exists.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 29, 2026, 6:39 p.m.