Triple
T4336298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bivalvia |
E97470
|
entity |
| Predicate | sensoryOrgans |
P50711
|
FINISHED |
| Object | poorly developed head |
—
|
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: poorly developed head | Statement: [Bivalvia, sensoryOrgans, poorly developed head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensoryOrgans Context triple: [Bivalvia, sensoryOrgans, poorly developed head]
-
A.
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.
-
B.
hasSensoryOrgans
chosen
Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
-
C.
senses
Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
-
D.
hasSpecializedOrgan
Indicates that an entity possesses a distinct organ adapted for a particular specialized function or role.
-
E.
mainOrganOf
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as an organism or system).
- 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.