Triple
T36764048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola C121 |
E908285
|
entity |
| Predicate | supportsDataConnectivity |
P127948
|
FINISHED |
| Object | no packet data |
—
|
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: no packet data | Statement: [Motorola C121, supportsDataConnectivity, no packet data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataConnectivity Context triple: [Motorola C121, supportsDataConnectivity, no packet data]
-
A.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
-
B.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
C.
supportsBlackBerryConnect
Indicates that an entity is compatible with and can operate using the BlackBerry Connect software or service.
-
D.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
E.
supportsDataExchange
chosen
Indicates that one entity enables or facilitates the transfer or sharing of data with another entity.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.