Triple
T28740226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypermastigida |
E731215
|
entity |
| Predicate | isSymbiotic |
P165278
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hypermastigida, isSymbiotic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSymbiotic Context triple: [Hypermastigida, isSymbiotic, true]
-
A.
containsSymbioticAssociationsWith
Indicates that one entity includes or encompasses another entity with which it maintains a symbiotic (mutually dependent or beneficial) biological relationship.
-
B.
symbiontType
Indicates the specific kind or category of symbiotic relationship that exists between associated organisms.
-
C.
isSympatheticTo
Indicates that one entity feels or expresses compassion, understanding, or emotional support toward another entity.
-
D.
isMicroorganism
Indicates that an entity is a microscopic living organism, such as a bacterium, virus, fungus, or protozoan.
-
E.
actsSynergisticallyWith
Indicates that two entities interact in a way that enhances or amplifies each other's effects or outcomes beyond what they would achieve independently.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b2b1808190a9f7c80eef2efa99 |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 6:02 a.m.