Triple
T10835555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathartes |
E255745
|
entity |
| Predicate | usesSense |
P53283
|
FINISHED |
| Object | olfaction to locate carrion |
—
|
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: olfaction to locate carrion | Statement: [Cathartes, usesSense, olfaction to locate carrion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSense Context triple: [Cathartes, usesSense, olfaction to locate carrion]
-
A.
hasSensation
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
-
B.
senses
chosen
Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
-
C.
sensingAction
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
-
D.
usesIntelligence
Indicates that an entity applies mental abilities such as reasoning, problem-solving, or understanding to perform an action or achieve a goal.
-
E.
targetSense
Indicates that one entity is the intended or actual target, focus, or endpoint of another entity’s action, attention, or effect.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d746fdefd4819099772efbd4f302cb |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.