Triple
T28740233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypermastigida |
E731215
|
entity |
| Predicate | relationshipToHost |
P202274
|
FINISHED |
| Object | mutualistic symbiont |
—
|
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: mutualistic symbiont | Statement: [Hypermastigida, relationshipToHost, mutualistic symbiont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHost Context triple: [Hypermastigida, relationshipToHost, mutualistic symbiont]
-
A.
relationshipToMain
Indicates that an entity has a specified type of relationship or association to a primary or main entity.
-
B.
relationshipToParent
Indicates the specific familial or social role an entity has in relation to its parent entity.
-
C.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
D.
relationshipToPH
Indicates a specified type of relationship or association that an entity has to public health (PH).
-
E.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
- 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_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
| PDg | Predicate description generation | batch_6a006be382308190811a8ee29c262ba1 |
completed | May 10, 2026, 11:28 a.m. |
Created at: April 28, 2026, 6:02 a.m.