Triple
T27769385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Bank Corporation |
E701698
|
entity |
| Predicate | hadClientele |
P163231
|
FINISHED |
| Object | corporate clients |
—
|
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: corporate clients | Statement: [Swiss Bank Corporation, hadClientele, corporate clients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadClientele Context triple: [Swiss Bank Corporation, hadClientele, corporate clients]
-
A.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
B.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
C.
hadCommon
Indicates that two or more entities shared the same attribute, experience, or element in common.
-
D.
hadIndex
Indicates that one entity possessed or was associated with a particular index (such as a numerical or reference position) at a given time or in a given context.
-
E.
hadBase
Indicates that an entity maintained or operated from a particular base location or primary site.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6379527cc8190b835dcf330096a64 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:33 p.m.