Triple
T6520099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantonal banks |
E148357
|
entity |
| Predicate | typicalGuaranteeProvider |
P32141
|
FINISHED |
| Object | respective canton |
—
|
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: respective canton | Statement: [Cantonal banks, typicalGuaranteeProvider, respective canton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGuaranteeProvider Context triple: [Cantonal banks, typicalGuaranteeProvider, respective canton]
-
A.
guaranteeProvider
chosen
Indicates that one entity serves as the party that provides or issues a guarantee for another entity or obligation.
-
B.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
C.
typicalProvider
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
-
D.
typeOfInsurer
Indicates the specific category or classification of an insurer in relation to an insurance policy or coverage.
-
E.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad92c624819086dbb12b4f6b78d3 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.