Triple
T7426720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gesellschaft mit beschränkter Haftung |
E171384
|
entity |
| Predicate | canHaveSingleShareholder |
P76929
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gesellschaft mit beschränkter Haftung, canHaveSingleShareholder, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHaveSingleShareholder Context triple: [Gesellschaft mit beschränkter Haftung, canHaveSingleShareholder, yes]
-
A.
majorShareholderOf
Indicates that one entity owns a controlling or significantly large portion of another entity’s shares or equity.
-
B.
hasShareClass
Indicates that an entity is associated with a specific class or category of shares that defines distinct rights or characteristics of ownership.
-
C.
hasMajorShareholderHistory
Indicates that an entity has had one or more major shareholders at some point in its history.
-
D.
ownershipStructure
Indicates how ownership or control is distributed among entities within an organization or asset.
-
E.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3055b7881908269ab909c5a85b5 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.