Triple
T6003320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLY |
E133646
|
entity |
| Predicate | ownershipForm |
P21682
|
FINISHED |
| Object | publicly traded corporation |
—
|
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: publicly traded corporation | Statement: [LLY, ownershipForm, publicly traded corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipForm Context triple: [LLY, ownershipForm, publicly traded corporation]
-
A.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
B.
ownershipEnd
Indicates the point or event at which an entity’s ownership of another entity ceases or is terminated.
-
C.
ownershipStart
Indicates the point in time at which an entity begins to own or hold legal possession of another entity.
-
D.
ownershipCharacteristic
Indicates that one entity possesses a particular quality, attribute, or condition specifically in its role as an owner of another entity.
-
E.
ownershipModel
chosen
Indicates the type or structure of ownership relationship that governs how control, rights, or shares are held between entities.
- 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.