Triple
T27982449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada lynx |
E706657
|
entity |
| Predicate | earTuftFunction |
P84341
|
FINISHED |
| Object | enhanced hearing or communication (hypothesized) |
—
|
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: enhanced hearing or communication (hypothesized) | Statement: [Canada lynx, earTuftFunction, enhanced hearing or communication (hypothesized)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earTuftFunction Context triple: [Canada lynx, earTuftFunction, enhanced hearing or communication (hypothesized)]
-
A.
hasEarTufts
chosen
Indicates that the subject possesses noticeable tufts of hair or feathers on its ears.
-
B.
earType
Indicates the specific kind or classification of ears associated with an entity.
-
C.
hasEars
Indicates that an entity possesses ears as a physical feature.
-
D.
earPosition
Indicates the spatial orientation or placement of an ear relative to a reference point or object.
-
E.
earLength
Indicates the length of an entity’s ear(s), typically as a measurable physical attribute.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b6a5fec81908e73597e2413bb1e |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:45 p.m.