Triple
T28760317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somewhere in the Hills |
E731791
|
entity |
| Predicate | isOnMedium |
P54385
|
FINISHED |
| Object | audio recording |
—
|
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: audio recording | Statement: [Somewhere in the Hills, isOnMedium, audio recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnMedium Context triple: [Somewhere in the Hills, isOnMedium, audio recording]
-
A.
isFromMedium
Indicates that something originates from, is derived from, or was obtained via a particular medium or channel.
-
B.
occursInMedium
chosen
Indicates that an event, process, or interaction takes place within or is hosted by a particular medium or environment.
-
C.
basedOnMedium
Indicates that one entity is derived from, adapted from, or created using another entity as its source medium or foundational material.
-
D.
hasPageMedium
Indicates that a page or document is associated with a particular physical or digital medium through which it is presented or stored.
-
E.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:11 a.m.