Triple
T8519703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norway rat |
E201664
|
entity |
| Predicate | hearingAbility |
P83091
|
FINISHED |
| Object | sensitive to ultrasound |
—
|
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: sensitive to ultrasound | Statement: [Norway rat, hearingAbility, sensitive to ultrasound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearingAbility Context triple: [Norway rat, hearingAbility, sensitive to ultrasound]
-
A.
hearingImpairment
Indicates that an entity has a reduced or impaired ability to hear compared to typical auditory function.
-
B.
hearingType
Indicates the type or category of a hearing event or proceeding that takes place.
-
C.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
D.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
E.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
- F. None of above. chosen
Provenance (4 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe627de908190b463da0f26da4ffb |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:16 p.m.