Triple
T27572748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLNS |
E696075
|
entity |
| Predicate | networkServiceUser |
P165085
|
FINISHED |
| Object | transport layer protocols in OSI |
—
|
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: transport layer protocols in OSI | Statement: [CLNS, networkServiceUser, transport layer protocols in OSI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkServiceUser Context triple: [CLNS, networkServiceUser, transport layer protocols in OSI]
-
A.
networkService
Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
-
B.
networkServed
Indicates that a network provides connectivity or services to a particular entity or set of entities.
-
C.
serviceNetwork
Indicates that one entity is part of, connected to, or operates within a particular service-oriented network or system.
-
D.
serviceUser
Indicates that one entity is a user or consumer of a service provided by another entity.
-
E.
usedByNetwork
Indicates that something is utilized or operated by a particular network.
- F. None of above. chosen
Provenance (4 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 1:44 p.m.