Triple
T3872059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caenorhabditis elegans |
E92409
|
entity |
| Predicate | bodyCavityType |
P21284
|
FINISHED |
| Object | pseudocoelomate |
—
|
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: pseudocoelomate | Statement: [Caenorhabditis elegans, bodyCavityType, pseudocoelomate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyCavityType Context triple: [Caenorhabditis elegans, bodyCavityType, pseudocoelomate]
-
A.
hasBodyCavity
chosen
Indicates that an organism possesses an internal body cavity or space within its body structure.
-
B.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
C.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
D.
stomachType
Indicates the kind or classification of stomach an entity has, typically describing its structural or functional type.
-
E.
usesBodyPart
Indicates that an entity performs an action or function by employing a specific body part as a means or tool.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec5691148190b469af0bee9154db |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.