Triple
T5313991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aktiengesellschaft |
E119100
|
entity |
| Predicate | ownershipDividedInto |
P6497
|
FINISHED |
| Object | shares |
—
|
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: shares | Statement: [Aktiengesellschaft, ownershipDividedInto, shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipDividedInto Context triple: [Aktiengesellschaft, ownershipDividedInto, shares]
-
A.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
B.
divisionImplications
Indicates the consequences, outcomes, or effects that result from a particular division or separation between entities.
-
C.
dividedBetween
chosen
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
D.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
E.
sharesCustodyWith
Indicates that two or more parties jointly hold legal responsibility and decision-making authority for the care and upbringing of the same dependent, typically a child.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:54 p.m.