Triple
T36848960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himalayan musk deer |
E910624
|
entity |
| Predicate | hornsOrAntlers |
P20069
|
FINISHED |
| Object | lacks antlers |
—
|
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: lacks antlers | Statement: [Himalayan musk deer, hornsOrAntlers, lacks antlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hornsOrAntlers Context triple: [Himalayan musk deer, hornsOrAntlers, lacks antlers]
-
A.
antlersPresentIn
Indicates that antlers are physically present within or on the specified location or entity.
-
B.
hasHorns
chosen
Indicates that an entity possesses horns as a physical feature.
-
C.
antlerType
Indicates the specific kind or classification of antlers that an entity possesses or is associated with.
-
D.
hornsDedicatedTo
Indicates that certain horns are formally devoted or consecrated to a particular deity, person, or purpose.
-
E.
antlersFeed
Indicates a feeding interaction where antlers are the source or medium through which nourishment is provided to another entity.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.