Triple
T28740211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypermastigida |
E731215
|
entity |
| Predicate | symbiontOf |
P18579
|
FINISHED |
| Object | wood-eating insects |
—
|
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: wood-eating insects | Statement: [Hypermastigida, symbiontOf, wood-eating insects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbiontOf Context triple: [Hypermastigida, symbiontOf, wood-eating insects]
-
A.
symbiontType
Indicates the specific kind or category of symbiotic relationship that exists between associated organisms.
-
B.
containsSymbioticAssociationsWith
chosen
Indicates that one entity includes or encompasses another entity with which it maintains a symbiotic (mutually dependent or beneficial) biological relationship.
-
C.
cohabitsWith
Indicates that two entities live together in the same dwelling or shared residence.
-
D.
hasCompanionSpecies
Indicates that one entity is accompanied by, or exists in association with, another entity of a different species.
-
E.
biotaDerivedFrom
Indicates that one biological entity originates from, or is derived from, another biological source or organism.
- 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_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. |
Created at: April 28, 2026, 6:02 a.m.