Triple
T6649604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exor N.V. |
E150785
|
entity |
| Predicate | portfolioDiversification |
P14738
|
FINISHED |
| Object | multi-sector |
—
|
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: multi-sector | Statement: [Exor N.V., portfolioDiversification, multi-sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portfolioDiversification Context triple: [Exor N.V., portfolioDiversification, multi-sector]
-
A.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an entity.
-
B.
diversifiedIn
chosen
Indicates that an entity has expanded its involvement, investments, or activities across multiple different areas, sectors, or asset types.
-
C.
folio
Indicates that one entity is a specific page, leaf, or numbered side within a larger bound or paginated document associated with another entity.
-
D.
investmentOptions
Indicates that one entity offers, defines, or is associated with possible ways another entity can allocate resources or capital.
-
E.
investmentScope
Indicates the range or boundaries of activities, assets, or sectors that an investment is intended or allowed to cover.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.