Triple
T18293161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T Recommendation G.992.1 |
E438164
|
entity |
| Predicate | publicationDomain |
P1753
|
FINISHED |
| Object | fixed access 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: fixed access networks | Statement: [ITU-T Recommendation G.992.1, publicationDomain, fixed access networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationDomain Context triple: [ITU-T Recommendation G.992.1, publicationDomain, fixed access networks]
-
A.
publishingDomain
Indicates the domain or organization responsible for publishing or disseminating the associated content or resource.
-
B.
fieldOfPublication
chosen
Indicates the academic or topical area in which a work is published.
-
C.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
D.
publicationScope
Indicates the extent, audience, or boundaries within which something (such as a work, data, or information) is made publicly available or distributed.
-
E.
publicationBody
Indicates the organization or entity that serves as the publishing body responsible for issuing the referenced work.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50100d6488190bbe73668df9c4046 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.