Triple
T5479827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5G NR |
E123441
|
entity |
| Predicate | hasDeploymentOption |
P55169
|
FINISHED |
| Object | macro cells |
—
|
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: macro cells | Statement: [5G NR, hasDeploymentOption, macro cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeploymentOption Context triple: [5G NR, hasDeploymentOption, macro cells]
-
A.
hasDeployment
Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
-
B.
deploymentOption
chosen
Indicates the available or chosen way in which something (such as a system, service, or component) can be deployed or made operational.
-
C.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
D.
providesOption
Indicates that one entity makes a particular choice, alternative, or configuration available to another entity.
-
E.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.