Triple
T37449926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudomonas |
E930646
|
entity |
| Predicate | pigmentProduction |
P109796
|
FINISHED |
| Object | produces water-soluble pigments in some species |
—
|
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: produces water-soluble pigments in some species | Statement: [Pseudomonas, pigmentProduction, produces water-soluble pigments in some species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pigmentProduction Context triple: [Pseudomonas, pigmentProduction, produces water-soluble pigments in some species]
-
A.
hasPigment
chosen
Indicates that one entity contains, incorporates, or is characterized by a particular pigment.
-
B.
pigmentation
Indicates the presence, type, or degree of coloration in or on an entity.
-
C.
primaryPigment
Indicates that one pigment is the main or dominant colorant used or present in relation to another entity.
-
D.
secondaryPigment
Indicates that one pigment functions as a secondary or supporting color relative to another primary pigment in a given context.
-
E.
primaryColorProduction
Indicates that an entity is responsible for producing or generating a primary color (such as red, blue, or yellow) in some context.
- 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.