Triple
T29992176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DZ Bank |
E761909
|
entity |
| Predicate | hasInternationalActivities |
P197979
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [DZ Bank, hasInternationalActivities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalActivities Context triple: [DZ Bank, hasInternationalActivities, yes]
-
A.
hasInternationalEvent
Indicates that an entity hosts, organizes, or is associated with an event involving participants or significance across multiple countries.
-
B.
hasInternationalAchievements
Indicates that an entity has attained notable accomplishments or recognition at an international level.
-
C.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given entity.
-
D.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
E.
hadInternationalAffiliation
Indicates that an entity was formally associated or connected with an organization, institution, or body based in a foreign country or operating across national borders.
- F. None of above. chosen
Provenance (4 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_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: April 29, 2026, 6:39 p.m.