Triple
T35719294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCIR System D |
E1032422
|
entity |
| Predicate | audioSystemDesignation |
P81036
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [CCIR System D, audioSystemDesignation, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioSystemDesignation Context triple: [CCIR System D, audioSystemDesignation, D]
-
A.
systemDesignation
chosen
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
B.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
-
C.
audioBrand
Indicates a relationship where one entity serves as the audio-related brand or sound identity associated with another entity.
-
D.
audioStack
Indicates that one audio element is layered or queued on top of another within an ordered audio sequence or mix.
-
E.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.