Triple
T13484487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3390 |
E318457
|
entity |
| Predicate | hasPhysicalConnector |
P68076
|
FINISHED |
| Object | Nokia proprietary charging port |
—
|
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: Nokia proprietary charging port | Statement: [Nokia 3390, hasPhysicalConnector, Nokia proprietary charging port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalConnector Context triple: [Nokia 3390, hasPhysicalConnector, Nokia proprietary charging port]
-
A.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
B.
hasPhysicalInterface
chosen
Indicates that one entity provides or includes a tangible, hardware-based connection point or medium through which another entity can physically interact or communicate.
-
C.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
-
D.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
-
E.
hasUSBConnectorType
Indicates the specific type or standard of USB connector associated with a device or component.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3a15b48190b63fb59e926a97ae |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.