Triple
T24632998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giovanni Agnelli B.V. |
E609727
|
entity |
| Predicate | hasShareholderRoleIn |
P121928
|
FINISHED |
| Object | Exor N.V. |
—
|
NE NERFINISHED |
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: Exor N.V. | Statement: [Giovanni Agnelli B.V., hasShareholderRoleIn, Exor N.V.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShareholderRoleIn Context triple: [Giovanni Agnelli B.V., hasShareholderRoleIn, Exor N.V.]
-
A.
isShareholderOf
chosen
Indicates that one entity owns shares or equity in another entity, giving it a financial stake and certain associated rights in that entity.
-
B.
hasShareholdersFrom
Indicates that an entity has shareholders who originate from or are associated with a specified country, region, or organization.
-
C.
hasCapitalOwnerRole
Indicates that an entity holds the role or status of owning capital in relation to another entity or asset.
-
D.
hasStakeholder
Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
-
E.
canHaveMultipleShareholders
Indicates that an entity is permitted to have more than one shareholder at the same time.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.