Triple
T23650518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kymriah |
E584153
|
entity |
| Predicate | firstEMAApprovalDate |
P68695
|
FINISHED |
| Object | 2018-08-27 |
—
|
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: 2018-08-27 | Statement: [Kymriah, firstEMAApprovalDate, 2018-08-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEMAApprovalDate Context triple: [Kymriah, firstEMAApprovalDate, 2018-08-27]
-
A.
wasFirstApprovedIn
chosen
Indicates the time or context in which something (such as a proposal, product, or document) received its initial official approval.
-
B.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
C.
firstSignalReceivedDate
Indicates the date on which an entity first received a particular signal.
-
D.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
E.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
- 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.