Triple
T22062794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEF |
E545193
|
entity |
| Predicate | supportsNetworkGeneration |
P130227
|
FINISHED |
| Object | 5G |
—
|
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: 5G | Statement: [NEF, supportsNetworkGeneration, 5G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNetworkGeneration Context triple: [NEF, supportsNetworkGeneration, 5G]
-
A.
supportsGeneration
chosen
Indicates that one entity enables, facilitates, or is compatible with the creation or production of another entity or outcome.
-
B.
supportedNetwork
Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
-
C.
supportsNetworkingModel
Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
-
D.
networkGeneration
Indicates the creation or formation of a network, specifying that entities are involved in establishing or generating connections within a network structure.
-
E.
supportsNetworkingLibraries
Indicates that an entity provides compatibility with or functionality for using networking libraries.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285e8c688190b701e417893cc148 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.