Triple
T19661385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Televisor mechanical television system |
E472088
|
entity |
| Predicate | audioTransmission |
P136860
|
FINISHED |
| Object | separate radio set for sound |
—
|
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: separate radio set for sound | Statement: [Televisor mechanical television system, audioTransmission, separate radio set for sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioTransmission Context triple: [Televisor mechanical television system, audioTransmission, separate radio set for sound]
-
A.
audioStreaming
Indicates that one entity is transmitting audio data in real time for another entity to receive or play back.
-
B.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
-
C.
soundRecordingBy
Indicates that a sound recording was created, performed, or produced by a particular agent (such as an artist, band, or producer).
-
D.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
E.
supportsPushToTalk
Indicates that an entity provides or is compatible with push-to-talk functionality for initiating communication.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414a667c81909aad04a737773c7e |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.