Triple
T37659542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 7110 |
E937684
|
entity |
| Predicate | doesNotSupportConnectivity |
P36910
|
FINISHED |
| Object | Bluetooth |
—
|
NE NERFINISHED |
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: Bluetooth | Statement: [Nokia 7110, doesNotSupportConnectivity, Bluetooth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotSupportConnectivity Context triple: [Nokia 7110, doesNotSupportConnectivity, Bluetooth]
-
A.
doNotSupport
Indicates that one entity withholds help, approval, or endorsement from another entity or action.
-
B.
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.
-
C.
connectivityFeatures
chosen
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
D.
hasNoConnectionType
Indicates that there is explicitly no defined type or category of connection between the related entities.
-
E.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.