Triple
T14337305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eumetopias |
E355496
|
entity |
| Predicate | hasSensoryFeature |
P24994
|
FINISHED |
| Object | well-developed hearing |
—
|
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: well-developed hearing | Statement: [Eumetopias, hasSensoryFeature, well-developed hearing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSensoryFeature Context triple: [Eumetopias, hasSensoryFeature, well-developed hearing]
-
A.
hasSensation
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
-
B.
providesSensoryEffects
Indicates that one entity causes or contributes to sensory experiences or perceptions in another entity.
-
C.
hasSensoryOrgans
Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
-
D.
sensitivityFeature
chosen
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
E.
hasSensor
Indicates that one entity is equipped with, contains, or uses a particular sensor.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c2241e48190a0c626b3d741966a |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.