Triple
T20301124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imfinzi |
E505480
|
entity |
| Predicate | indicatedSetting |
P139583
|
FINISHED |
| Object | locally advanced cancer |
—
|
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: locally advanced cancer | Statement: [Imfinzi, indicatedSetting, locally advanced cancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatedSetting Context triple: [Imfinzi, indicatedSetting, locally advanced cancer]
-
A.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
B.
inductionSetting
Indicates the conditions or configuration under which an induction process or inductive operation is carried out.
-
C.
usedAsSettingFor
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
-
D.
knownAsSettingFor
Indicates that something is recognized or regarded as the typical or notable setting or backdrop for something else.
-
E.
basedOnSetting
Indicates that one entity is derived from, influenced by, or constructed using the setting or contextual environment defined by another entity.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6770c700c81909da247cef0d0f1eb |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:17 a.m.