Triple
T21571338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neodermata |
E532289
|
entity |
| Predicate | endoparasiticGroups |
P16820
|
FINISHED |
| Object | most Trematoda |
—
|
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: most Trematoda | Statement: [Neodermata, endoparasiticGroups, most Trematoda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endoparasiticGroups Context triple: [Neodermata, endoparasiticGroups, most Trematoda]
-
A.
parasitizes
Indicates a relationship in which one organism lives on or in another organism, deriving nutrients or benefits at the host’s expense.
-
B.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
C.
invertebrateFauna
Indicates that the subject has or is associated with a collection or community of animals lacking a vertebral column (invertebrates).
-
D.
includesPestGroup
Indicates that one entity contains or encompasses a specified group or category of pests within its scope or composition.
-
E.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cd50188190b44eb25fb87312bb |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.