Triple
T27945694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xerox Network Systems |
E700872
|
entity |
| Predicate | protocolFamilyType |
P4615
|
FINISHED |
| Object | proprietary protocol suite |
—
|
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: proprietary protocol suite | Statement: [Xerox Network Systems, protocolFamilyType, proprietary protocol suite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolFamilyType Context triple: [Xerox Network Systems, protocolFamilyType, proprietary protocol suite]
-
A.
protocolFamily
chosen
Indicates that one protocol belongs to, or is categorized under, a broader protocol family or group.
-
B.
networkFamily
Indicates a relationship where entities belong to the same network grouping or family, typically sharing common infrastructure, protocols, or organizational affiliation.
-
C.
socketFamily
Indicates the type of communication protocol family (e.g., IPv4, IPv6, Unix domain) that a socket belongs to.
-
D.
interfaceFamily
Indicates that one interface belongs to, or is categorized within, a particular family or group of related interfaces.
-
E.
addressFamily
Indicates the type of network address family (such as IPv4 or IPv6) associated with or used by an entity in a communication context.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:21 p.m.