Triple
T24378038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMI |
E614531
|
entity |
| Predicate | blueChipCoverage |
P38809
|
FINISHED |
| Object | major Swiss blue-chip companies |
—
|
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: major Swiss blue-chip companies | Statement: [SMI, blueChipCoverage, major Swiss blue-chip companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blueChipCoverage Context triple: [SMI, blueChipCoverage, major Swiss blue-chip companies]
-
A.
blueChipExposure
Indicates the extent to which an entity is invested in or financially exposed to established, high-quality "blue chip" assets or companies.
-
B.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
C.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
D.
typeOfCoverage
chosen
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
E.
hasBlueChipStatus
Indicates that an entity holds recognized blue-chip status, signifying it is a leading, stable, and highly reputable performer within its domain.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d96e7c8190b2f33a8fd12c32c6 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.