Triple
T18052750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pallas's cat |
E431959
|
entity |
| Predicate | earPosition |
P129641
|
FINISHED |
| Object | set low on the sides of the head |
—
|
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: set low on the sides of the head | Statement: [Pallas's cat, earPosition, set low on the sides of the head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earPosition Context triple: [Pallas's cat, earPosition, set low on the sides of the head]
-
A.
speakerPosition
Indicates the spatial or contextual location of a speaker relative to other entities or a reference frame during an utterance or event.
-
B.
conePosition
Indicates the spatial position or placement of a cone relative to a reference frame or environment.
-
C.
bearerPosition
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
-
D.
axePosition
Indicates the spatial location or orientation of an axe relative to a reference point or object.
-
E.
headsetHapticsLocation
Indicates the specific physical area or position on a headset where haptic feedback is applied or experienced.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c0ff580c8190bc3ca04025476255 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:26 a.m.