Triple
T363281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genentech |
E7901
|
entity |
| Predicate | formerListedCompany |
P12397
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Genentech, formerListedCompany, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerListedCompany Context triple: [Genentech, formerListedCompany, true]
-
A.
charteredCompany
Indicates that a company has been formally established and granted specific rights or privileges through an official charter, typically by a government or sovereign authority.
-
B.
formerParentCompany
Indicates that one entity previously served as the parent company of another but no longer holds that status.
-
C.
formerEmployer
Indicates that one entity previously employed the other but no longer does so.
-
D.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
E.
formerName
Indicates that an entity was previously known by a different name in the past.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95c843c8190b2aba9af6e869ba1 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2c44408190946267525c88e811 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.