Triple
T17240718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6310 |
E418488
|
entity |
| Predicate | pcConnectivityInterfaces |
P112572
|
FINISHED |
| Object | serial cable |
—
|
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: serial cable | Statement: [Nokia 6310, pcConnectivityInterfaces, serial cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pcConnectivityInterfaces Context triple: [Nokia 6310, pcConnectivityInterfaces, serial cable]
-
A.
portConnections
chosen
Indicates that there exists a connection or linkage between two ports or interfaces.
-
B.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
C.
connectivityMode
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
-
D.
interconnectionType
Indicates the specific kind or nature of relationship that links two or more entities together.
-
E.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e1f385c8190ae44e702923b6f66 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.