Triple
T10086141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignicoccus hospitalis |
E215224
|
entity |
| Predicate | lipidComposition |
P12468
|
FINISHED |
| Object | ether-linked archaeal membrane lipids |
—
|
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: ether-linked archaeal membrane lipids | Statement: [Ignicoccus hospitalis, lipidComposition, ether-linked archaeal membrane lipids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lipidComposition Context triple: [Ignicoccus hospitalis, lipidComposition, ether-linked archaeal membrane lipids]
-
A.
membraneLipidType
chosen
Indicates the specific type or class of lipid that composes or is associated with a membrane.
-
B.
fattyAcid
Indicates a relationship where one entity is a fatty acid component, derivative, or participant in a process involving another entity.
-
C.
milkComposition
Indicates the specific nutrients and components that make up a given sample of milk.
-
D.
membraneLipidSideChains
Indicates that one entity is a membrane lipid and the other represents its attached hydrocarbon side chains.
-
E.
typicalFatContent
Indicates the usual or characteristic amount of fat contained in something, such as a food or product.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04609748190987a9364a387fa61 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.