Triple
T1503345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSCO |
E33844
|
entity |
| Predicate | issuerSpecialization |
P29435
|
FINISHED |
| Object | computer networking |
—
|
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: computer networking | Statement: [CSCO, issuerSpecialization, computer networking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerSpecialization Context triple: [CSCO, issuerSpecialization, computer networking]
-
A.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
B.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
C.
issuerBrandName
Indicates the brand name associated with the entity that issues a product, document, or instrument.
-
D.
issuerCUSIP
Indicates that the subject entity is identified as the issuer associated with the specified CUSIP code.
-
E.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
| PDg | Predicate description generation | batch_69a90582f2548190bc0a6bdcd6d9d015 |
completed | March 5, 2026, 4:24 a.m. |
Created at: March 4, 2026, 7:24 p.m.