Triple
T6649609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exor N.V. |
E150785
|
entity |
| Predicate | corporateGovernanceModel |
P2995
|
FINISHED |
| Object | one-tier board |
—
|
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: one-tier board | Statement: [Exor N.V., corporateGovernanceModel, one-tier board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateGovernanceModel Context triple: [Exor N.V., corporateGovernanceModel, one-tier board]
-
A.
governanceModel
chosen
Indicates the type or structure of authority, decision-making, and control that defines how an entity is directed and overseen.
-
B.
hasCorporateGovernanceCode
Indicates that an entity is associated with, follows, or is governed by a specific corporate governance code or set of governance rules.
-
C.
corporateStructure
Indicates how entities are organized, controlled, and related within a corporate hierarchy or ownership structure.
-
D.
governancePattern
Indicates the characteristic way in which authority, decision-making, and control are structured and exercised within or between entities.
-
E.
governanceDocumentType
Indicates the specific category or type of formal governance document that defines rules, policies, or oversight for an entity or process.
- 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.