Triple
T17806073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.726 |
E444560
|
entity |
| Predicate | intendedNetworkType |
P3937
|
FINISHED |
| Object | digital telephone networks |
—
|
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: digital telephone networks | Statement: [G.726, intendedNetworkType, digital telephone networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedNetworkType Context triple: [G.726, intendedNetworkType, digital telephone networks]
-
A.
intendedNetwork
Indicates the network that an entity is planned, designed, or expected to connect to or operate within.
-
B.
networkType
chosen
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
C.
networkIntended
Indicates that one entity is designed or purposed to be used within, connected to, or operate over a particular network or networking context.
-
D.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
-
E.
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.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4880385b48190b8dea0f05dfa1300 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.