Triple
T36764063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola C121 |
E908285
|
entity |
| Predicate | supportsRILReplacement |
P205035
|
FINISHED |
| Object | yes via OsmocomBB |
—
|
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: yes via OsmocomBB | Statement: [Motorola C121, supportsRILReplacement, yes via OsmocomBB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRILReplacement Context triple: [Motorola C121, supportsRILReplacement, yes via OsmocomBB]
-
A.
supportsEsim
Indicates that one entity provides compatibility with, or the ability to use, an embedded SIM (eSIM) for another entity.
-
B.
supportsGSM
Indicates that one entity provides compatibility with or operational support for GSM (Global System for Mobile communications) technology for another entity.
-
C.
requiresCarrierSupport
Indicates that performing or enabling this action depends on support or approval from a carrier (e.g., a mobile network operator).
-
D.
supportsSIMInstruction
Indicates that one entity is capable of handling or executing a specified SIM (Subscriber Identity Module) instruction for another entity.
-
E.
supportsOTA
Indicates that one entity enables or is compatible with over-the-air (OTA) updates or operations for another entity.
- F. None of above. chosen
Provenance (4 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.