Triple
T6003322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLY |
E133646
|
entity |
| Predicate | issuerEmployeeType |
P11918
|
FINISHED |
| Object | research scientists |
—
|
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: research scientists | Statement: [LLY, issuerEmployeeType, research scientists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerEmployeeType Context triple: [LLY, issuerEmployeeType, research scientists]
-
A.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
B.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
C.
employmentType
chosen
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
-
D.
issuerCEO
Indicates that the subject entity serves as the chief executive officer (CEO) of the issuer entity.
-
E.
issuerAlsoKnownFor
Indicates that the issuer is additionally recognized or notable for another role, activity, or attribute beyond their primary identified capacity.
- 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.