Triple
T23650577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasigna |
E584154
|
entity |
| Predicate | isSecondGeneration |
P41139
|
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: [Tasigna, isSecondGeneration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSecondGeneration Context triple: [Tasigna, isSecondGeneration, true]
-
A.
secondGeneration
chosen
Indicates that one entity belongs to the second generation relative to another, such as being the child of a first-generation member in a lineage or sequence.
-
B.
secondGenerationEnd
Indicates the point in time or event at which the second generation of a lineage, process, or system concludes.
-
C.
secondGenerationName
Indicates that the object is the name given to the second generation derived from the subject.
-
D.
hasSecondGenerationLeader
Indicates that an entity is led or governed by a leader belonging to its second generation of leadership.
-
E.
secondGenerationStartYear
Indicates the calendar year in which the second generation of something (e.g., a product, model, or series) begins.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b357d1108190802bc29e0ed7f097 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.