Triple
T37660445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiftung & Co. KG |
E937705
|
entity |
| Predicate | ownershipControl |
P181787
|
FINISHED |
| Object | exercised by foundation 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: exercised by foundation board | Statement: [Stiftung & Co. KG, ownershipControl, exercised by foundation board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipControl Context triple: [Stiftung & Co. KG, ownershipControl, exercised by foundation board]
-
A.
ownershipConfers
Indicates that possessing or owning something grants the owner certain rights, powers, or privileges over it.
-
B.
ownershipStart
Indicates the point in time at which an entity begins to own or hold legal possession of another entity.
-
C.
ownershipRule
chosen
Indicates a rule or constraint that governs who may own, control, or have legal rights over a given entity or resource.
-
D.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
E.
ownershipEnd
Indicates the point or event at which an entity’s ownership of another entity ceases or is terminated.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:18 p.m.