Triple
T2630208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatr Mobile |
E59613
|
entity |
| Predicate | SIMType |
P28070
|
FINISHED |
| Object | bring-your-own-device compatible |
—
|
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: bring-your-own-device compatible | Statement: [Chatr Mobile, SIMType, bring-your-own-device compatible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SIMType Context triple: [Chatr Mobile, SIMType, bring-your-own-device compatible]
-
A.
simType
chosen
Indicates that two entities share the same or a comparable type, category, or classification.
-
B.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
C.
packageType
Indicates the classification or category of packaging associated with an item or shipment.
-
D.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
E.
MMSINumber
Indicates a relationship where a mobile subscriber is associated with a specific Mobile Station International ISDN Number (MSISDN) used to identify their phone line in a mobile network.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.