Triple
T26657992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | camelback hills |
E666562
|
entity |
| Predicate | sensationType |
P93007
|
FINISHED |
| Object | sustained airtime |
—
|
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: sustained airtime | Statement: [camelback hills, sensationType, sustained airtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensationType Context triple: [camelback hills, sensationType, sustained airtime]
-
A.
sensoryModality
Indicates the type of sensory channel (e.g., visual, auditory, tactile) through which an experience, perception, or information is received or processed.
-
B.
hasSensation
chosen
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
-
C.
senses
Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
-
D.
sensorySystem
Indicates that one entity functions as the sensory system (or part of it) of another, enabling the detection and processing of internal or external stimuli.
-
E.
sensoryCommunication
Indicates a relationship where one entity conveys or exchanges information with another through sensory signals or perception-based means.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:35 a.m.