Triple
T29100118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | π/4 DQPSK |
E736616
|
entity |
| Predicate | usesQuadratureComponents |
P166317
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [π/4 DQPSK, usesQuadratureComponents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesQuadratureComponents Context triple: [π/4 DQPSK, usesQuadratureComponents, true]
-
A.
hasQuadrants
Indicates that something is divided into four distinct sections or regions, typically arranged as quadrants.
-
B.
usesBasisFunctions
Indicates that one entity represents, models, or computes another entity by expressing it as a combination of specified basis functions.
-
C.
isQuadraticIn
Indicates that one quantity depends on another through a quadratic (second-degree polynomial) relationship in that variable.
-
D.
quadratureUncertainties
Indicates that the uncertainties of related quantities are combined using quadrature (i.e., by summing their variances or squared contributions).
-
E.
usesQuantification
Indicates that one entity employs or applies a system of quantification (such as numerical or measurable assessment) to another entity or context.
- 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_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. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:11 a.m.