Triple
T16212045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaetognatha |
E393487
|
entity |
| Predicate | hasSensoryStructure |
P50711
|
FINISHED |
| Object | ciliary fence receptors |
—
|
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: ciliary fence receptors | Statement: [Chaetognatha, hasSensoryStructure, ciliary fence receptors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSensoryStructure Context triple: [Chaetognatha, hasSensoryStructure, ciliary fence receptors]
-
A.
hasSensoryOrgans
chosen
Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
-
B.
hasSensation
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
-
C.
sensorySystem
Indicates that one entity functions as the sensory system (or part of it) of another, enabling the detection and processing of internal or external stimuli.
-
D.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
E.
hasSpecializedOrgan
Indicates that an entity possesses a distinct organ adapted for a particular specialized function or role.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.