Triple
T37521942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraxane |
E932801
|
entity |
| Predicate | hasTargetProcess |
P157412
|
FINISHED |
| Object | cell division |
—
|
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: cell division | Statement: [Abraxane, hasTargetProcess, cell division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetProcess Context triple: [Abraxane, hasTargetProcess, cell division]
-
A.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
B.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
C.
targetsProcess
chosen
Indicates that one entity is directed toward affecting, influencing, or acting upon a specific process.
-
D.
hasSubProcess
Indicates that one process is composed of or includes another process as a subordinate or component step.
-
E.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.