Triple
T29100124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | π/4 DQPSK |
E736616
|
entity |
| Predicate | bitPerSymbol |
P4121
|
FINISHED |
| Object | 2 bits per symbol |
—
|
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: 2 bits per symbol | Statement: [π/4 DQPSK, bitPerSymbol, 2 bits per symbol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitPerSymbol Context triple: [π/4 DQPSK, bitPerSymbol, 2 bits per symbol]
-
A.
parityBits
Indicates that there is an association between data and the parity bits used to detect or correct errors in that data.
-
B.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
C.
bitOrder
Indicates the ordering or sequence of bits within a binary representation, such as which bit positions are considered first or most significant.
-
D.
bitRepresentation
Indicates that one entity is the binary (bit-level) representation or encoding of another entity.
-
E.
bitSynchronizationSupport
Indicates whether a system, device, or protocol provides mechanisms to align and maintain timing at the bit level between communicating entities.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66184e9208190a66378cac527bca9 |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:11 a.m.