Triple
T17076137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3i Group |
E414351
|
entity |
| Predicate | roleInSubsidiary |
P28882
|
FINISHED |
| Object | investment manager of 3i Infrastructure plc |
—
|
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: investment manager of 3i Infrastructure plc | Statement: [3i Group, roleInSubsidiary, investment manager of 3i Infrastructure plc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSubsidiary Context triple: [3i Group, roleInSubsidiary, investment manager of 3i Infrastructure plc]
-
A.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another organization.
-
B.
coreSubsidiaryOf
Indicates that one entity is a primary or central subsidiary that is owned or controlled by another entity.
-
C.
hasSubsidiaryRoleInGroup
chosen
Indicates that an entity holds a secondary or supporting role within a specified group.
-
D.
subsidiaryOrAsset
Indicates that one entity is owned, controlled, or held as a subsidiary company or asset by another entity.
-
E.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc559388190b685504cca6ed62b |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.