Triple
T19773663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takeda Pharmaceutical Company |
E474950
|
entity |
| Predicate | TakedaIsmValuesInclude |
P137287
|
FINISHED |
| Object | Integrity |
—
|
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: Integrity | Statement: [Takeda Pharmaceutical Company, TakedaIsmValuesInclude, Integrity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TakedaIsmValuesInclude Context triple: [Takeda Pharmaceutical Company, TakedaIsmValuesInclude, Integrity]
-
A.
hasDaishido
Indicates that an entity possesses, includes, or is associated with a Daishidō (a specific hall, building, or designated area).
-
B.
TaishoNumber
Indicates that an entity is associated with a specific Taisho catalog or numbering system identifier.
-
C.
traditionallyIncludes
Indicates that something customarily or historically contains or incorporates something else as a standard or expected part.
-
D.
includesSee
Indicates that one entity’s scope, content, or experience contains or encompasses the act of seeing or visual perception involving another entity.
-
E.
isTraditionalProductOf
Indicates that something is a customary or historically established product originating from a particular place, culture, or group.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535e450c8190a2628245ae0d0bd3 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.