Triple
T6003300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLY |
E133646
|
entity |
| Predicate | beneficialOwnerType |
P22506
|
FINISHED |
| Object | public shareholders |
—
|
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: public shareholders | Statement: [LLY, beneficialOwnerType, public shareholders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneficialOwnerType Context triple: [LLY, beneficialOwnerType, public shareholders]
-
A.
beneficialOwner
Indicates that one entity is the ultimate beneficiary of ownership rights or economic interest in another entity or asset, even if the ownership is held indirectly or through intermediaries.
-
B.
beneficiaryType
chosen
Indicates the type or category of beneficiary that receives or is intended to receive the benefit or outcome of an action or resource.
-
C.
organizationTypeOfHolder
Indicates that a specified organization serves as the type or category of the holder in the given relationship.
-
D.
organizationTypeOfOwner
Indicates the type or category of organization that owns a given entity.
-
E.
namedPartyType
Indicates the specific role or category that a referenced party holds within a given context or relationship.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.