Triple
T19027197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinius Trust |
E465638
|
entity |
| Predicate | roleInSchibsted |
P133615
|
FINISHED |
| Object | controlling shareholder |
—
|
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: controlling shareholder | Statement: [Tinius Trust, roleInSchibsted, controlling shareholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSchibsted Context triple: [Tinius Trust, roleInSchibsted, controlling shareholder]
-
A.
laborMarketRole
Indicates the role, function, or position an entity holds within the labor market, such as its job type, employment status, or economic participation category.
-
B.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
C.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
D.
sectorEmploymentRole
Indicates the specific role or function an entity holds within a particular employment sector or industry.
-
E.
socialRoleInWork
Indicates the role or position an entity holds within a work-related or professional social context.
- F. None of above. chosen
Provenance (4 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d73dc404819092059e496662d151 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.