Triple
T17477387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostracoda |
E425573
|
entity |
| Predicate | hasSensoryOrgan |
P50711
|
FINISHED |
| Object | compound eyes in many species |
—
|
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: compound eyes in many species | Statement: [Ostracoda, hasSensoryOrgan, compound eyes in many species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSensoryOrgan Context triple: [Ostracoda, hasSensoryOrgan, compound eyes in many species]
-
A.
hasSensoryOrgans
chosen
Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
-
B.
hasSpecializedOrgan
Indicates that an entity possesses a distinct organ adapted for a particular specialized function or role.
-
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.
hasAntennae
Indicates that one entity possesses or is equipped with antennae as a physical feature.
-
E.
hasSensation
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bd865081909b5f84405c40ff14 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.