Triple
T3841567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lophotrochozoa |
E93460
|
entity |
| Predicate | hasCoelomType |
P7384
|
FINISHED |
| Object | coelomate in many groups |
—
|
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: coelomate in many groups | Statement: [Lophotrochozoa, hasCoelomType, coelomate in many groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoelomType Context triple: [Lophotrochozoa, hasCoelomType, coelomate in many groups]
-
A.
coelomType
chosen
Indicates the type or structure of the body cavity (coelom) an organism possesses in relation to its body wall and internal organs.
-
B.
coelomFormation
Indicates the developmental process by which a true body cavity (coelom) forms within an organism’s embryonic tissues.
-
C.
hasBodyCavity
Indicates that an organism possesses an internal body cavity or space within its body structure.
-
D.
hasPhylum
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
-
E.
hasSubphylum
Indicates that one biological entity is classified as a subphylum within the broader taxonomic grouping of 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.