Triple
T6003493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alimta |
E133650
|
entity |
| Predicate | requiresSupplementationWith |
P20051
|
FINISHED |
| Object | folic acid |
—
|
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: folic acid | Statement: [Alimta, requiresSupplementationWith, folic acid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSupplementationWith Context triple: [Alimta, requiresSupplementationWith, folic acid]
-
A.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
B.
hasSupplement
chosen
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
-
C.
containsSupplicationOf
Indicates that one entity includes or expresses a plea, request, or supplicatory appeal directed toward another entity.
-
D.
requiresCompatibilityWith
Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.