Triple
T14503054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N72 |
E340192
|
entity |
| Predicate | usbConnectivity |
P104380
|
FINISHED |
| Object | USB via Pop-Port 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: USB via Pop-Port cable | Statement: [Nokia N72, usbConnectivity, USB via Pop-Port cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usbConnectivity Context triple: [Nokia N72, usbConnectivity, USB via Pop-Port cable]
-
A.
hasUSBConnectorType
Indicates the specific type or standard of USB connector associated with a device or component.
-
B.
usbFeatures
chosen
Indicates that there exists a relationship specifying the USB-related capabilities or characteristics supported by an entity.
-
C.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
-
D.
hasUSBDevicePortCount
Indicates the number of USB device ports that an entity possesses or supports.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e0f9048190a2d266cfa4f9dfb6 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.