Triple
T21264905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frequency Division Duplex |
E524099
|
entity |
| Predicate | hasDesignParameter |
P89378
|
FINISHED |
| Object | uplink–downlink frequency separation |
—
|
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: uplink–downlink frequency separation | Statement: [Frequency Division Duplex, hasDesignParameter, uplink–downlink frequency separation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignParameter Context triple: [Frequency Division Duplex, hasDesignParameter, uplink–downlink frequency separation]
-
A.
designParameter
chosen
Indicates that one entity serves as a design-related parameter, constraint, or configurable setting that influences how another entity is specified, structured, or implemented.
-
B.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
hasDesignIntent
Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by another entity.
-
E.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735ea74e0819099d724de95996c90 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 4 p.m.