Triple
T37449902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudomonas |
E930646
|
entity |
| Predicate | metabolicCharacteristic |
P12476
|
FINISHED |
| Object | metabolically versatile |
—
|
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: metabolically versatile | Statement: [Pseudomonas, metabolicCharacteristic, metabolically versatile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metabolicCharacteristic Context triple: [Pseudomonas, metabolicCharacteristic, metabolically versatile]
-
A.
metabolismType
Indicates the kind of metabolic process or pathway an entity uses to obtain and transform energy or nutrients.
-
B.
metabolismTrend
Indicates how an entity’s metabolic rate or activity is changing over time (e.g., increasing, decreasing, or remaining stable).
-
C.
metabolicDiversity
chosen
Indicates the range and variety of metabolic pathways or processes that an entity can perform or participate in.
-
D.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
E.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.