Triple
T28400377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OC-3 |
E719379
|
entity |
| Predicate | totalChannels |
P82796
|
FINISHED |
| Object | 3 STS-1 channels |
—
|
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: 3 STS-1 channels | Statement: [OC-3, totalChannels, 3 STS-1 channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalChannels Context triple: [OC-3, totalChannels, 3 STS-1 channels]
-
A.
numberOfFullRangeChannels
Indicates the total count of channels that operate over the complete available range of values or frequencies.
-
B.
maxChannels
Indicates the maximum number of channels that can be used, created, or active within a given context or system.
-
C.
numberOfAdditionalChannels
Indicates the quantity of extra channels added beyond a base or default set in a given context.
-
D.
polyphonicChannels
Indicates that an entity supports or involves multiple independent audio or musical channels that can sound simultaneously (polyphony).
-
E.
hasChannelCount
chosen
Indicates that an entity is associated with a specific number of channels.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 1:19 a.m.