Triple
T16318580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Escherichia coli OP50 |
E396233
|
entity |
| Predicate | auxotrophyFor |
P122677
|
FINISHED |
| Object | uracil |
—
|
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: uracil | Statement: [Escherichia coli OP50, auxotrophyFor, uracil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auxotrophyFor Context triple: [Escherichia coli OP50, auxotrophyFor, uracil]
-
A.
nutritionMode
Indicates the way an entity obtains or processes nutrients for sustenance or growth.
-
B.
deficiencyAssociatedWith
Indicates an association where a lack or insufficiency of one entity is related to the occurrence, presence, or severity of another entity.
-
C.
antinutritionalFactor
Indicates that something functions as an antinutritional factor, meaning it interferes with the digestion, absorption, or utilization of nutrients.
-
D.
regulatesNutrient
Indicates a relationship where one entity controls, modulates, or maintains the levels, availability, or flow of a nutrient in another entity or system.
-
E.
metabolismType
Indicates the kind of metabolic process or pathway an entity uses to obtain and transform energy or nutrients.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b3e3e081908a996b3e57ca4e32 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.