Triple
T4336401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monoplacophora |
E97472
|
entity |
| Predicate | coelom |
P7384
|
FINISHED |
| Object | reduced coelom |
—
|
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: reduced coelom | Statement: [Monoplacophora, coelom, reduced coelom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coelom Context triple: [Monoplacophora, coelom, reduced coelom]
-
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.
hasPharyngealSlits
Indicates that an organism possesses pharyngeal slits, openings in the pharynx that connect the throat to the external environment or a cavity, typically used for filter-feeding or respiration.
-
E.
swimBladder
Indicates that an entity possesses or is associated with a swim bladder, an internal gas-filled organ used to control buoyancy in water.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516af43081908393fd0dad3d9382 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.