Triple
T36193386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaeista |
E1047050
|
entity |
| Predicate | containsOrganismsWith |
P203102
|
FINISHED |
| Object | multicellular thalli |
—
|
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: multicellular thalli | Statement: [Phaeista, containsOrganismsWith, multicellular thalli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsOrganismsWith Context triple: [Phaeista, containsOrganismsWith, multicellular thalli]
-
A.
includesOrganisms
Indicates that one entity contains, encompasses, or has as members one or more specified organisms.
-
B.
hasOrganism
Indicates that one entity is an organism associated with, contained in, or otherwise possessed by another entity.
-
C.
containsModelOrganisms
Indicates that one entity includes or incorporates model organisms as part of its contents or composition.
-
D.
detectsOrganism
Indicates that one entity identifies, discovers, or observes the presence of another organism.
-
E.
containsSymbioticAssociationsWith
Indicates that one entity includes or encompasses another entity with which it maintains a symbiotic (mutually dependent or beneficial) biological relationship.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
| PDg | Predicate description generation | batch_6a01203a1c188190874d87d148dfa8e4 |
completed | May 11, 2026, 12:18 a.m. |
Created at: May 3, 2026, 4:08 p.m.