Triple
T5771076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NB-IoT |
E127331
|
entity |
| Predicate | supportsDeploymentMode |
P55169
|
FINISHED |
| Object | standalone |
—
|
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: standalone | Statement: [NB-IoT, supportsDeploymentMode, standalone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeploymentMode Context triple: [NB-IoT, supportsDeploymentMode, standalone]
-
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.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
C.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
D.
deploymentOption
chosen
Indicates the available or chosen way in which something (such as a system, service, or component) can be deployed or made operational.
-
E.
deploymentModel
Indicates the type or manner in which a system, service, or resource is deployed or made available (e.g., on-premises, cloud, hybrid).
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.