Triple
T261173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Systems |
E5543
|
entity |
| Predicate | coreBusiness |
P6749
|
FINISHED |
| Object | Design of networking hardware |
—
|
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: Design of networking hardware | Statement: [Cisco Systems, coreBusiness, Design of networking hardware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreBusiness Context triple: [Cisco Systems, coreBusiness, Design of networking hardware]
-
A.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
-
B.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
C.
underlyingCompanyBusinessFocus
chosen
Indicates the primary industry, sector, or type of business activity that the underlying company is focused on.
-
D.
company
Indicates that an entity is a business organization engaged in commercial, industrial, or professional activities.
-
E.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.