Triple
T2138678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tecentriq |
E46710
|
entity |
| Predicate | administrationSchedule |
P3309
|
FINISHED |
| Object | given every 2 to 4 weeks depending on regimen |
—
|
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: given every 2 to 4 weeks depending on regimen | Statement: [Tecentriq, administrationSchedule, given every 2 to 4 weeks depending on regimen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrationSchedule Context triple: [Tecentriq, administrationSchedule, given every 2 to 4 weeks depending on regimen]
-
A.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
B.
typicalSchedule
chosen
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
D.
scheduleCount
Indicates the number of scheduled instances or events associated with a given entity or context.
-
E.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.