Triple
T6908422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P Europe 350 |
E159868
|
entity |
| Predicate | blueChipFocus |
P24414
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [S&P Europe 350, blueChipFocus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blueChipFocus Context triple: [S&P Europe 350, blueChipFocus, true]
-
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.
isBlueChipIndex
chosen
Indicates that an index is composed primarily of large, well-established, financially stable companies considered blue-chip stocks.
-
C.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
D.
hasBlueChipStatus
Indicates that an entity holds recognized blue-chip status, signifying it is a leading, stable, and highly reputable performer within its domain.
-
E.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9be98748190b5cb698e66e3aa42 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.