Triple
T4161478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electrical Audio |
E91542
|
entity |
| Predicate | recordingMedium |
P53051
|
FINISHED |
| Object | analog tape |
—
|
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: analog tape | Statement: [Electrical Audio, recordingMedium, analog tape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingMedium Context triple: [Electrical Audio, recordingMedium, analog tape]
-
A.
notableRecordingMedium
Indicates that an entity is notably recorded, documented, or expressed using a particular medium or format.
-
B.
phonographicType
Indicates the specific kind or category of phonographic recording or medium associated with an entity.
-
C.
hasPhysicalMedium
chosen
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
D.
recordingType
Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
-
E.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.